dbcve.org
CWE-338Weakness · CWE-338

CVE-2026-11832

CRITICAL · 9.1 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Dancer2::Plugin::Auth::OAuth versions before 0.22 for Perl default to a predictable nonce. The default nonce was generated using an MD5 hash of the epoch time, which is predictable.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Dancer2::Plugin::Auth::OAuth versions before 0.22 use a predictable nonce generated from an MD5 hash of epoch time, making authentication tokens forgeable.

MitigationUpgrade to version 0.22 or later which implements proper cryptographic nonce generation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Dancer2::Plugin::Auth::OAuth is installed
    Run 'perldoc -l Dancer2::Plugin::Auth::OAuth' or check your cpanfile/local::lib for this module
    Affected if Module is present in the environment
  2. Determine installed version of Dancer2::Plugin::Auth::OAuth
    Run 'perldoc Dancer2::Plugin::Auth::OAuth' or use 'cpan -D Dancer2::Plugin::Auth::OAuth' to retrieve the version number
    Affected if Version is below 0.22 or cannot be determined (treat as vulnerable)
  3. Verify OAuth plugin is loaded in your Dancer2 application
    Inspect your Dancer2 app .pm file for 'with "Dancer2::Plugin::Auth::OAuth"' or check for 'plugin: Auth::OAuth' in your app configuration YAML
    Affected if The OAuth plugin is loaded and version is below 0.22

You are affected if Dancer2::Plugin::Auth::OAuth is installed with a version lower than 0.22 and the OAuth authentication plugin is actively used in your application.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 0.22 or later which implements proper cryptographic nonce generation.

Recommended fix High confidence

Version 0.22 of Dancer2::Plugin::Auth::OAuth

  1. Check the current installed version of Dancer2::Plugin::Auth::OAuth using: cpan -D Dancer2::Plugin::Auth::OAuth or cpanm Dancer2::Plugin::Auth::OAuth --version
  2. Upgrade to version 0.22 using your preferred CPAN client: cpanm Dancer2::Plugin::Auth::OAuth 0.22 or cpan Dancer2::Plugin::Auth::OAuth
  3. Verify the upgrade was successful by checking the installed version matches 0.22 or later
  4. Restart any Perl applications using this module to ensure they load the updated version
  5. Review your application logs after restart to confirm the OAuth authentication continues to function correctly

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11832 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-11832 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data