# CVE-2026-11832: Dancer2::Plugin::Auth::OAuth versions before 0.22 for Perl default to a predictable nonce

> Predictable nonce generation in Dancer2 OAuth plugin allows attackers to bypass OAuth security checks.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jun 2026
- **Updated:** 16 Jun 2026
- **Also known as:** GHSA-h3g4-wmrw-rm63

## What is CVE-2026-11832?

CVE-2026-11832 is a critical vulnerability in BIAFRA Dancer2::Plugin::Auth::OAuth, published on 15 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-338 (Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG))

## Which versions are affected by CVE-2026-11832?


## How do I fix CVE-2026-11832?

No fix has been published for CVE-2026-11832 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-11832 being exploited?

There is no known exploitation of CVE-2026-11832 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-11832 and fix it if it is affected.

What it is: CVE-2026-11832 is a critical vulnerability in BIAFRA Dancer2::Plugin::Auth::OAuth, published on 15 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-11832 in the wild and no public exploit code.

Affected product: BIAFRA Dancer2::Plugin::Auth::OAuth. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-11832/ (Markdown: https://insights.sbomify.com/CVE-2026-11832/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-11832
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-11832
- OSV: https://osv.dev/vulnerability/CVE-2026-11832

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-11832/
Summaries are generated and may contain mistakes; the official description above is the record.