# CVE-2026-19363: lmammino oidc-authorizer Lambda Authorizer handler.rs log file

> Remote attackers can obtain sensitive credentials and JWT claims from CloudWatch Logs due to verbose logging in the OIDC Lambda Authorizer.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/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:** 11 Aug 2026
- **Also known as:** GHSA-fwrx-97hw-xg2r

## What is CVE-2026-19363?

CVE-2026-19363 is a medium-severity 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 was found in lmammino oidc-authorizer up to 0.4.0. Impacted is an unknown function of the file src/handler.rs of the component Lambda Authorizer. The manipulation results in sensitive information in log files. The attack can be executed remotely. `src/handler.rs` logs raw Authorization header values and complete bearer tokens/JWTs on authentication failure paths, potentially exposing credentials through CloudWatch Logs. `src/models.rs` serializes the complete validated JWT claims set with `serde_json::to_string(token_claims).unwrap()` and propagates it through `context["jwtClaims"]` to downstream integrations. This code performs serialization, not deserialization, and does not process attacker-controlled `jwtClaims` input. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-19363 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19363 is a medium-severity 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: There is no known exploitation of CVE-2026-19363 in the wild and no public exploit code.

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-19363/ (Markdown: https://insights.sbomify.com/CVE-2026-19363/index.md)
```

## Sources

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

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