Monitor vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
7.5
httpsig-hyper Digest Verification May Fail to Detect Message Tampering
CVE-2026-26275
GHSA-7v42-g35v-xrch
Summary
Some applications using httpsig-hyper may incorrectly accept tampered messages due to a bug in the library's digest verification process. This can lead to undetected changes to message content. To fix this, update to version 0.0.23 of httpsig-hyper or implement additional signature validation layers to ensure message integrity.
What to do
- Update httpsig-hyper to version 0.0.23.
Affected software
| Vendor | Product | Affected versions | Fix available |
|---|---|---|---|
| – | httpsig-hyper | <= 0.0.23 | 0.0.23 |
| junkurihara | httpsig-hyper | <= 0.0.23 | – |
Original title
Improper Digest Verification in httpsig-hyper May Allow Message Integrity Bypass
Original description
### Impact
An issue was discovered in `httpsig-hyper` where Digest header verification could incorrectly succeed due to misuse of Rust's `matches!` macro. Specifically, the comparison:
```rust
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.
---
### Patches
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.
---
### Workarounds
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.
---
### References
- PR: https://github.com/junkurihara/httpsig-rs/pull/14
- Follow-up hardening and test additions: https://github.com/junkurihara/httpsig-rs/pull/15
An issue was discovered in `httpsig-hyper` where Digest header verification could incorrectly succeed due to misuse of Rust's `matches!` macro. Specifically, the comparison:
```rust
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.
---
### Patches
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.
---
### Workarounds
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.
---
### References
- PR: https://github.com/junkurihara/httpsig-rs/pull/14
- Follow-up hardening and test additions: https://github.com/junkurihara/httpsig-rs/pull/15
nvd CVSS3.1
7.5
Vulnerability type
CWE-354
CWE-697
- https://github.com/junkurihara/httpsig-rs/pull/15 Issue Tracking Patch
- https://github.com/junkurihara/httpsig-rs/security/advisories/GHSA-7v42-g35v-xrc... Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-26275
- https://github.com/advisories/GHSA-7v42-g35v-xrch
- https://github.com/junkurihara/httpsig-rs/commit/5533f596c650377e02f4aa9e3eb8dba... Patch
- https://github.com/junkurihara/httpsig-rs/commit/65cbd19b395180a4bba09a89746c4b1... Patch
- https://github.com/junkurihara/httpsig-rs/pull/14 Issue Tracking Patch
Published: 17 Feb 2026 · Updated: 11 Mar 2026 · First seen: 6 Mar 2026