Signature compromise via unenforced JWS key lengths
Published Aug 7, 2025 · Updated Aug 12, 2025
Insufficient key strength in ruby-jwt allows remote attackers to compromise JWS signatures created with undersized HMAC or RSA keys. The JWS signing and verification paths accept keys without enforcing minimum lengths, leaving key strength to the application and OpenSSL. Reachability requires an application to select an undersized key; the supplier disputes that key-size policy belongs in the library.
Summary
What happened
Insufficient key strength in ruby-jwt allows remote attackers to compromise JWS signatures created with undersized HMAC or RSA keys. The JWS signing and verification paths accept keys without enforcing minimum lengths, leaving key strength to the application and OpenSSL. Reachability requires an application to select an undersized key; the supplier disputes that key-size policy belongs in the library.
The record
- CVE
- CVE-2025-45765
- Published
- Aug 7, 2025
- Updated
- Aug 12, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-326, CAPEC-192, CAPEC-20, CAPEC-112
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 7, 2025CVE publishedPublication date reported by the CVE source.
- Aug 12, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo