CVE-2026-72889 Affecting libnet-oauth-perl package, versions <0.33-1


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.45% (37th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-DEBIAN14-LIBNETOAUTHPERL-18961604
  • published19 Aug 2026
  • disclosed19 Aug 2026

Introduced: 19 Aug 2026

CVE-2026-72889  (opens in a new tab)

How to fix?

Upgrade Debian:14 libnet-oauth-perl to version 0.33-1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream libnet-oauth-perl package and not the libnet-oauth-perl package as distributed by Debian. See How to fix? for Debian:14 relevant fixed versions and status.

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.