CVE-2026-72889

verify resolves the signature method class from the signaturemethod parameter of the incoming message. signaturemethod 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 consumersecret and tokensecret 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.

Database specific

{
    "unresolved_ranges": [
        {
            "source": "AFFECTED_FIELD",
            "extracted_events": [
                {
                    "fixed": "0.33"
                }
            ]
        },
        {
            "source": "DESCRIPTION",
            "extracted_events": [
                {
                    "fixed": "0.33"
                }
            ]
        }
    ],
    "cwe_ids": [
        "CWE-347",
        "CWE-757"
    ],
    "cna_assigner": "CPANSec",
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/72xxx/CVE-2026-72889.json"
}

References

Affected packages

Git / github.com/vurtdev/net-oauth

Affected ranges

Type

GIT

Repo

https://github.com/vurtdev/net-oauth

Events

Introduced

Fixed

c467adf45c8d77ac4b92ad78b3eebf949252ba7f

Database specific

Show details

{
    "source": "REFERENCES"
}

Affected versions

v0.*

v0.29

v0.30

v0.31

v0.32

Database specific

source

"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-72889.json"