CVE-2026-26275
httpsig-hyper has Improper Digest Verification that May Allow Message Integrity Bypass
Description
httpsig-hyper is a hyper extension for http message signatures. An issue was discovered in `httpsig-hyper` prior to version 0.0.23 where Digest header verification could incorrectly succeed due to misuse of Rust's `matches!` macro. Specifically, the comparison `if matches!(digest, _expected_digest)` treated `_expected_digest` as a pattern binding rather than a value comparison, resulting in unconditional success of the match expression. As a consequence, digest verification could incorrectly return success even when the computed digest did not match the expected value. Applications relying on Digest verification as part of HTTP message signature validation may therefore fail to detect message body modification. The severity depends on how the library is integrated and whether additional signature validation layers are enforced. This issue has been fixed in `httpsig-hyper` 0.0.23. The fix replaces the incorrect `matches!` usage with proper value comparison and additionally introduces constant-time comparison for digest verification as defense-in-depth. Regression tests have also been added to prevent reintroduction of this issue. Users are strongly advised to upgrade to the patched version. There is no reliable workaround without upgrading. Users who cannot immediately upgrade should avoid relying solely on Digest verification for message integrity and ensure that full HTTP message signature verification is enforced at the application layer.
INFO
Published Date :
Feb. 19, 2026, 10:16 p.m.
Last Modified :
March 3, 2026, 5:44 p.m.
Remotely Exploit :
Yes !
Source :
[email protected]
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | HIGH | [email protected] | ||||
| CVSS 3.1 | HIGH | MITRE-CVE |
Solution
- Upgrade httpsig-hyper to version 0.0.23.
- Ensure full HTTP message signature validation.
- Avoid relying solely on Digest verification.
Public PoC/Exploit Available at Github
CVE-2026-26275 has a 1 public
PoC/Exploit available at Github.
Go to the Public Exploits tab to see the list.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-26275.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-26275 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-26275
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
# مستودع asrar-mared هذا هو المستودع الرئيسي لمجموعة **المارد الرقمي**، نقطة التحكم المركزية التي تجمع كل المشاريع والميول التقنية تحت راية واحدة. يمثل الأساس الذي تُبنى عليه الفروع الأخرى، ويُدار منه كل شيء من تنظيم الكود إلى إدارة المجتمع. للاطلاع على المستودع: [asrar-mared](https://github.com/asrar-mared)
HTML CSS
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-26275 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-26275 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Mar. 03, 2026
Action Type Old Value New Value Added CPE Configuration OR *cpe:2.3:a:junkurihara:httpsig-hyper:*:*:*:*:*:rust:*:* versions up to (excluding) 0.0.23 Added Reference Type GitHub, Inc.: https://github.com/junkurihara/httpsig-rs/commit/5533f596c650377e02f4aa9e3eb8dba591b87370 Types: Patch Added Reference Type GitHub, Inc.: https://github.com/junkurihara/httpsig-rs/commit/65cbd19b395180a4bba09a89746c4b14ccb8d297 Types: Patch Added Reference Type GitHub, Inc.: https://github.com/junkurihara/httpsig-rs/pull/14 Types: Issue Tracking, Patch Added Reference Type GitHub, Inc.: https://github.com/junkurihara/httpsig-rs/pull/15 Types: Issue Tracking, Patch Added Reference Type GitHub, Inc.: https://github.com/junkurihara/httpsig-rs/security/advisories/GHSA-7v42-g35v-xrch Types: Vendor Advisory -
New CVE Received by [email protected]
Feb. 19, 2026
Action Type Old Value New Value Added Description httpsig-hyper is a hyper extension for http message signatures. An issue was discovered in `httpsig-hyper` prior to version 0.0.23 where Digest header verification could incorrectly succeed due to misuse of Rust's `matches!` macro. Specifically, the comparison `if matches!(digest, _expected_digest)` treated `_expected_digest` as a pattern binding rather than a value comparison, resulting in unconditional success of the match expression. As a consequence, digest verification could incorrectly return success even when the computed digest did not match the expected value. Applications relying on Digest verification as part of HTTP message signature validation may therefore fail to detect message body modification. The severity depends on how the library is integrated and whether additional signature validation layers are enforced. This issue has been fixed in `httpsig-hyper` 0.0.23. The fix replaces the incorrect `matches!` usage with proper value comparison and additionally introduces constant-time comparison for digest verification as defense-in-depth. Regression tests have also been added to prevent reintroduction of this issue. Users are strongly advised to upgrade to the patched version. There is no reliable workaround without upgrading. Users who cannot immediately upgrade should avoid relying solely on Digest verification for message integrity and ensure that full HTTP message signature verification is enforced at the application layer. Added CVSS V3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N Added CWE CWE-354 Added CWE CWE-697 Added Reference https://github.com/junkurihara/httpsig-rs/commit/5533f596c650377e02f4aa9e3eb8dba591b87370 Added Reference https://github.com/junkurihara/httpsig-rs/commit/65cbd19b395180a4bba09a89746c4b14ccb8d297 Added Reference https://github.com/junkurihara/httpsig-rs/pull/14 Added Reference https://github.com/junkurihara/httpsig-rs/pull/15 Added Reference https://github.com/junkurihara/httpsig-rs/security/advisories/GHSA-7v42-g35v-xrch