๐Ÿ” CVE Alert

CVE-2026-72889

CRITICAL 9.8

Net::OAuth versions before 0.33 for Perl allow the sender to choose the signature algorithm in verify

CVSS Score
9.8
EPSS Score
0.1%
EPSS Percentile
3th

Net::OAuth versions before 0.33 for Perl allow the sender to choose the signature algorithm in verify. verify resolves the signature method class from the signature_method parameter of the incoming message. signature_method is required on every request, so the algorithm used to check a signature is chosen by whoever sent it, and nothing lets the verifying party pin the method instead. When a message names HMAC-SHA1 or HMAC-SHA256, the key is derived from consumer_secret and token_secret rather than from the key the provider deployed. A provider deployed on RSA-SHA1 holds only the consumer public key, and RFC 5849 does not use consumer_secret for that method, so the required parameter is filled with a placeholder. A client that names HMAC-SHA1 instead has its signature checked against that placeholder, so a guessable one is enough to forge requests for any consumer key and token.

CWE CWE-347 CWE-757
Published Aug 19, 2026
Last Updated Aug 26, 2026
Stay Ahead of the Next One

Get instant alerts for

Be the first to know when new critical vulnerabilities are published โ€” delivered to Slack, Telegram or Discord.

Get Free Alerts โ†’ Free ยท No credit card ยท 60 sec setup

References

NVD โ†— CVE.org โ†— EPSS Data โ†—
github.com: https://github.com/vurtdev/Net-OAuth/security/advisories/GHSA-c8rm-g5cm-4pf5 github.com: https://github.com/vurtdev/Net-OAuth/commit/c467adf45c8d77ac4b92ad78b3eebf949252ba7f.patch metacpan.org: https://metacpan.org/release/RRWO/Net-OAuth-0.33/changes datatracker.ietf.org: https://datatracker.ietf.org/doc/html/rfc5849#section-3.4.2 datatracker.ietf.org: https://datatracker.ietf.org/doc/html/rfc5849#section-3.4.3 openwall.com: http://www.openwall.com/lists/oss-security/2026/08/19/2