Cyber Resilience

CVE-2025-59058

Published
12 September 2025
Modified
15 April 2026
CVSS Score v3.1 5.9
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS Score 0.0026 18th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2025-59058 is a medium-severity Observable Timing Discrepancy (CWE-208) vulnerability. Its CVSS base score is 5.9 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 18th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-13 (Cryptographic Protection) and SA-11 (Developer Testing and Evaluation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

httpsig-rs is a Rust implementation of IETF RFC 9421 http message signatures. Prior to version 0.0.19, the HMAC signature comparison is not timing-safe. This makes anyone who uses HS256 signature verification vulnerable to a timing attack that allows the attacker…

more

to forge a signature. Version 0.0.19 fixes the issue.

CWE(s)
CWE-208

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Why these techniques?

Timing-unsafe HMAC comparison in HTTP message signature verification directly enables remote signature forgery against applications using the library (public-facing HTTP services).

Confidence: HIGH · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-44368Shared CWE-208
CVE-2025-52457Shared CWE-208
CVE-2026-27882Shared CWE-208
CVE-2026-6656Shared CWE-208
CVE-2026-33129Shared CWE-208
CVE-2026-40194Shared CWE-208
CVE-2026-9537Shared CWE-208
CVE-2025-22234Shared CWE-208
CVE-2026-28464Shared CWE-208
CVE-2024-41828Shared CWE-208

Affected Assets

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SC-13 Cryptographic Protection
  • SA-11 Developer Testing and Evaluation
  • SA-15 Development Process, Standards, and Tools
Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V11.2.4

Mitigating Controls (NIST 800-53 r5) AI

SC-13 Cryptographic Protection good match
prevent

Mandates correct implementation of cryptographic mechanisms (HS256/HMAC signatures) that must employ constant-time comparison to prevent timing-based forgery.

SA-11 Developer Testing and Evaluation partial match
prevent

Requires developer testing and evaluation specifically for side-channel and timing vulnerabilities in cryptographic signature verification code.

SA-15 Development Process, Standards, and Tools partial match
prevent

Enforces use of secure development processes and coding standards that prohibit non-constant-time comparisons in security-critical functions such as HMAC verification.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require constant-time implementations that eliminate observable timing discrepancies.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.17 Clock synchronization none match
none

Consistent reference clocks limit the attacker's ability to measure or manipulate timing differences that could reveal internal state or processing paths.

References