VulnerabilityPublished 9 Aug 2026Updated 11 Aug 2026

CVE-2026-19363: lmammino oidc-authorizer · Sensitive Information in Log Files

Affects lmammino oidc-authorizerSource CVE Database V5

Compare

Public exploit available · CVSS 6.9 Medium · patch available : patch lmammino oidc-authorizer as a priority.

Data as of 7 Nov 2026, 23:24 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available

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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
lmamminooidc-authorizer	Affected 0.1 – 0.4.0 4 affected builds	Fixed in–
crates.iolmammino/oidc-authorizer`pkg:cargo/lmammino/oidc-authorizer`Other threats	Affected 0.1 – 0.4.0 4 affected builds	Fixed in–

CPE configurations (1)

cpe:2.3:a:lmammino:oidc-authorizer:*:*:*:*:*:*:*:*

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available for this vulnerability. Since the product is a cloud service, the vendor typically manages remediation server-side. Users should verify with the vendor advisory or service status that the patch has been applied. Until then, sensitive logging should be reviewed and minimized if possible to reduce exposure.

Description

CVE-2026-19363 is a medium severity vulnerability in lmammino oidc-authorizer up to version 0.4.0. It involves sensitive information exposure through log files due to logging raw Authorization header values and bearer tokens/JWTs on authentication failure. This can lead to credentials being exposed in CloudWatch Logs. The vulnerability affects the Lambda Authorizer component, specifically in the src/handler.rs and src/models.rs files. The vulnerability can be exploited remotely. A patch is available, and the product is a cloud service, so the vendor typically manages remediation. No known exploits are reported in the wild.

Impact

Sensitive information including raw Authorization headers and bearer tokens/JWTs can be exposed in log files (CloudWatch Logs), potentially allowing unauthorized parties to access credentials. This exposure could lead to compromise of authentication tokens. The vulnerability is remotely exploitable without authentication or user interaction. No known active exploitation is reported.

Summary

The vulnerability in lmammino oidc-authorizer (<=0.4.0) arises from logging sensitive data such as raw Authorization headers and bearer tokens/JWTs on authentication failure paths in src/handler.rs. Additionally, the complete validated JWT claims set is serialized and propagated downstream, which may expose sensitive information. The vulnerability allows remote attackers to potentially access sensitive credentials through CloudWatch Logs. The vendor was contacted but did not respond. The product is cloud-hosted, and a patch is available. The CVSS 4.0 score is 6.9 (medium severity), with network attack vector, low complexity, no privileges or user interaction required, and partial confidentiality impact.

References

Community reviews

Loading reviews…