Signature forgery via timing side channel
Published Aug 19, 2026 · Updated Aug 19, 2026
Observable timing discrepancy in verify in Net::OAuth before 0.33 allows remote attackers to forge OAuth signatures via timing analysis. The verify routines in the HMAC-SHA1, HMAC-SHA256, and PLAINTEXT signature methods compare the supplied and computed signatures with Perl's short-circuiting eq operator instead of a constant-time check, so rejection time leaks the length of the matching prefix; in PLAINTEXT mode, the compared value is the signature key itself. Reachability requires the ability to submit chosen OAuth messages and measure response timing, and the disclosed impact is bounded to signature recovery for HMAC methods and recovery of consumer_secret and token_secret for PLAINTEXT; RSA-SHA1 is not affected.
Summary
What happened
Observable timing discrepancy in verify in Net::OAuth before 0.33 allows remote attackers to forge OAuth signatures via timing analysis. The verify routines in the HMAC-SHA1, HMAC-SHA256, and PLAINTEXT signature methods compare the supplied and computed signatures with Perl's short-circuiting eq operator instead of a constant-time check, so rejection time leaks the length of the matching prefix; in PLAINTEXT mode, the compared value is the signature key itself. Reachability requires the ability to submit chosen OAuth messages and measure response timing, and the disclosed impact is bounded to signature recovery for HMAC methods and recovery of consumer_secret and token_secret for PLAINTEXT; RSA-SHA1 is not affected.
The record
- CVE
- CVE-2026-75589
- Published
- Aug 19, 2026
- Updated
- Aug 19, 2026
- Vendor
- Net-OAuth Project
- Product
- Net-OAuth
- Classifications
- CWE-208
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 19, 2026CVE publishedPublication date reported by the CVE source.
- Aug 19, 2026Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <0.33
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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