[From nobody Wed Aug 19 16:51:04 2026
Received: (at submit) by bugs.debian.org; 19 Aug 2026 12:17:44 +0000
X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
 (2024-03-25) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-10.9 required=4.0 tests=BAYES_00,FOURLA,
 FROMDEVELOPER,MD5_SHA1_SUM,NO_RELAYS,XMAILER_REPORTBUG autolearn=ham
 autolearn_force=no version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 21; hammy, 150; neutral, 83; spammy,
 0. spammytokens: hammytokens:0.000-+--XDebbugsCc,
 0.000-+--X-Debbugs-Cc, 0.000-+--H*F:U*carnil, 0.000-+--H*Ad:N*Bug,
 0.000-+--HTo:N*Debian
Return-path: &lt;carnil@debian.org&gt;
Received: via submission by buxtehude.debian.org with esmtp (Exim 4.96)
 (envelope-from &lt;carnil@debian.org&gt;) id 1wwfEk-001sol-0b
 for submit@bugs.debian.org; Wed, 19 Aug 2026 12:17:44 +0000
Content-Type: text/plain; charset=&quot;us-ascii&quot;
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Salvatore Bonaccorso &lt;carnil@debian.org&gt;
To: Debian Bug Tracking System &lt;submit@bugs.debian.org&gt;
Subject: libnet-oauth-perl: CVE-2026-72889
Message-ID: &lt;178714186113.2961725.9088836813207493638.reportbug@elende.valinor.li&gt;
X-Mailer: reportbug 13.2.0+nmu1
Date: Wed, 19 Aug 2026 14:17:41 +0200
Delivered-To: submit@bugs.debian.org

Source: libnet-oauth-perl
Version: 0.32-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: carnil@debian.org, Debian Security Team &lt;team@security.debian.org&gt;

Hi,

The following vulnerability was published for libnet-oauth-perl.

CVE-2026-72889[0]:
| 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.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities &amp; Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2026-72889
    https://www.cve.org/CVERecord?id=CVE-2026-72889
[1] https://lists.security.metacpan.org/cve-announce/msg/42818761/
[2] https://github.com/vurtdev/Net-OAuth/security/advisories/GHSA-c8rm-g5cm-4pf5
[3] https://github.com/vurtdev/Net-OAuth/commit/c467adf45c8d77ac4b92ad78b3eebf949252ba7f

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
]