CPANSA-Net-OAuth-2026-72889: Net-OAuth vulnerability
| Publisher | giterlizzi | Document category | csaf_security_advisory |
|---|---|---|---|
| Initial release date | 2026-08-19T00:00:00 | Engine | CSAF Perl Toolkit 0.26 |
| Current release date | 2026-08-19T00:00:00 | Build Date | |
| Current version | 1 | Status | final |
| CVSS v3.1 Base Score | 9.8 | Severity | Critical |
| Original language | Language | en | |
| Also referred to | |||
Vulnerability Description
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.
Vulnerabilities
CVE-2026-72889
Vulnerability DescriptionNet::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.
| Weakness | CWE-347 : Improper Verification of Cryptographic Signature |
|---|
Product status
Known affected
| Product | Score | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Net-OAuth less than 0.33 |
|
Fixed
- Net-OAuth greater than or equal 0.33
giterlizzi
Namespace: https://github.com/giterlizzi/
gdt@cpan.org
References
- CPANSA-Net-OAuth-2026-72889 JSON self
https://raw.githubusercontent.com/giterlizzi/perl-CPANSA-CSAF/develop/csaf/white/2026/cpansa-net-oauth-2026-72889.json - https://datatracker.ietf.org/doc/html/rfc5849#section-3.4.2 external
https://datatracker.ietf.org/doc/html/rfc5849#section-3.4.2 - https://datatracker.ietf.org/doc/html/rfc5849#section-3.4.3 external
https://datatracker.ietf.org/doc/html/rfc5849#section-3.4.3 - https://github.com/vurtdev/Net-OAuth/commit/c467adf45c8d77ac4b92ad78b3eebf949252ba7f.patch external
https://github.com/vurtdev/Net-OAuth/commit/c467adf45c8d77ac4b92ad78b3eebf949252ba7f.patch - https://github.com/vurtdev/Net-OAuth/security/advisories/GHSA-c8rm-g5cm-4pf5 external
https://github.com/vurtdev/Net-OAuth/security/advisories/GHSA-c8rm-g5cm-4pf5 - https://metacpan.org/release/RRWO/Net-OAuth-0.33/changes external
https://metacpan.org/release/RRWO/Net-OAuth-0.33/changes - http://www.openwall.com/lists/oss-security/2026/08/19/2 external
http://www.openwall.com/lists/oss-security/2026/08/19/2 - CVE-2026-72889 (NVD) external
https://nvd.nist.gov/vuln/detail/CVE-2026-72889
Revision history
| Version | Date of the revision | Summary of the revision |
|---|---|---|
| 1 | Wed Aug 19 00:00:00 2026 | First release |
Sharing rules
TLP:WHITE
For the TLP version see: https://www.first.org/tlp/