httpsig-hyper
Affected
- introduced
0, fixed0.0.23(semver)
Fixed versions
0.0.23
Fix
- Fixed version
0.0.23cargo update -p httpsig-hyper --precise 0.0.23
Advisory
Also known as: CVE-2026-26275
Improper Digest Verification in httpsig-hyper May Allow Message Integrity Bypass
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:
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.23The 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
High Basis: The source's own band: HIGH
0, fixed 0.0.23 (semver)0.0.23
0.0.23cargo update -p httpsig-hyper --precise 0.0.23Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0