Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%
Buy Us a Coffee

CVE-2026-72889— Net::OAuth versions before 0.33 for Perl allow the sender to choose the signature algorithm in verify

Quick assessment

Affected
CVE-2026-72889
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Net::OAuth 0.33 之前版本的 Perl 库中，攻击者可以在签名验证过程中自行选择签名算法。 在 函数中，签名方法类是从传入消息的 参数中解析得到的。由于所有请求都必须提供 参数，因此用于验证签名的算法实际上由发送方决定，而验证方无法强制锁定特定的签名方法。 当消息指定使用 HMAC-SHA1 或 HMAC-SHA256 时，签名密钥会从 和 派生，而不是使用服务提供商（provider）部署的密钥。 如果服务提供商部署的是 RSA-SHA1 签名方案，则其仅持有消费者的公钥。根据 RFC 5849，R

AI Predicted 9.8 Difficulty: Easy EPSS 0.11% · P2

Possible ATT&CK Techniques 1 AI

T1190 · Exploit Public-Facing Application

Affected Version Matrix 1

VendorProduct Version RangeStatus
None None < 0.33 affected

I. Basic Information for CVE-2026-72889

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Net::OAuth versions before 0.33 for Perl allow the sender to choose the signature algorithm in verify
Source: CVE Program / CVE List V5
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.
Source: CVE Program / CVE List V5
CVSS Information
N/A
Source: CVE Program / CVE List V5
Vulnerability Type
密码学签名的验证不恰当
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
- - 0 ~ 0.33 -

II. Public POCs for CVE-2026-72889

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-72889

请登录查看更多情报信息。

Patches & Fixes for CVE-2026-72889 (2)

Vendor Advisories for CVE-2026-72889 (1)

IV. Related Vulnerabilities

Same weakness: CWE-347

V. Comments for CVE-2026-72889

No comments yet

Leave a comment