# CVE-2026-19362: Denial of service in oidc-authorizer

> Remote attackers can cause denial of service in lmammino oidc-authorizer by manipulating the authorization token argument during header parsing.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-gv74-4w48-83fh

## What is CVE-2026-19362?

CVE-2026-19362 is a medium-severity denial of service vulnerability in lmammino oidc-authorizer, published on 9 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability has been found in lmammino oidc-authorizer 0.4.0. This issue affects the function parse_token_from_header of the file src/parse_token_from_header.rs of the component Authorization Header Parsing. The manipulation of the argument authorization_token leads to denial of service. Remote exploitation of the attack is possible. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-404 (Improper Resource Shutdown or Release)

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


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

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

## Is CVE-2026-19362 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19362 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19362 is a medium-severity denial of service vulnerability in lmammino oidc-authorizer, published on 9 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19362 exists.

Affected product: lmammino oidc-authorizer. 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-19362/ (Markdown: https://insights.sbomify.com/CVE-2026-19362/index.md)
```

## Sources

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

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