CVE-2026-40945: CWE-532: Insertion of Sensitive Information into Log File in oxia-db oxia
CVE-2026-40945 is a high-severity vulnerability in oxia versions prior to 0. 16. 2 where failed OIDC authentication attempts cause the full bearer token to be logged in plaintext at DEBUG level. This exposes sensitive JWT tokens in application logs and any connected log aggregation systems if debug logging is enabled in production environments. The vulnerability is fixed in version 0. 16. 2.
AI Analysis
Technical Summary
Oxia, a metadata store and coordination system, prior to version 0.16.2, logs the full bearer token in plaintext at DEBUG level when OIDC authentication fails. This behavior can lead to sensitive JWT tokens being exposed in logs and any log aggregation systems that collect these logs. The vulnerability is identified as CWE-532 (Insertion of Sensitive Information into Log File). It has a CVSS 4.0 score of 8.7 (high severity), indicating network attack vector, low attack complexity, no privileges or user interaction required, and high impact on confidentiality. The issue is resolved in oxia version 0.16.2.
Potential Impact
If debug logging is enabled in production on affected oxia versions (<0.16.2), sensitive bearer tokens (JWTs) are exposed in plaintext within application logs and any connected log aggregation infrastructure. This exposure could allow unauthorized parties with access to logs to obtain valid authentication tokens, potentially compromising system security. There are no known exploits in the wild at this time.
Mitigation Recommendations
Upgrade oxia to version 0.16.2 or later, where this vulnerability is fixed. Until upgrading, avoid enabling DEBUG level logging in production environments to prevent sensitive token exposure in logs. Patch status is not explicitly stated but the vendor has fixed the issue in version 0.16.2, so applying this official fix is recommended.
CVE-2026-40945: CWE-532: Insertion of Sensitive Information into Log File in oxia-db oxia
Description
CVE-2026-40945 is a high-severity vulnerability in oxia versions prior to 0. 16. 2 where failed OIDC authentication attempts cause the full bearer token to be logged in plaintext at DEBUG level. This exposes sensitive JWT tokens in application logs and any connected log aggregation systems if debug logging is enabled in production environments. The vulnerability is fixed in version 0. 16. 2.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Oxia, a metadata store and coordination system, prior to version 0.16.2, logs the full bearer token in plaintext at DEBUG level when OIDC authentication fails. This behavior can lead to sensitive JWT tokens being exposed in logs and any log aggregation systems that collect these logs. The vulnerability is identified as CWE-532 (Insertion of Sensitive Information into Log File). It has a CVSS 4.0 score of 8.7 (high severity), indicating network attack vector, low attack complexity, no privileges or user interaction required, and high impact on confidentiality. The issue is resolved in oxia version 0.16.2.
Potential Impact
If debug logging is enabled in production on affected oxia versions (<0.16.2), sensitive bearer tokens (JWTs) are exposed in plaintext within application logs and any connected log aggregation infrastructure. This exposure could allow unauthorized parties with access to logs to obtain valid authentication tokens, potentially compromising system security. There are no known exploits in the wild at this time.
Mitigation Recommendations
Upgrade oxia to version 0.16.2 or later, where this vulnerability is fixed. Until upgrading, avoid enabling DEBUG level logging in production environments to prevent sensitive token exposure in logs. Patch status is not explicitly stated but the vendor has fixed the issue in version 0.16.2, so applying this official fix is recommended.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-04-15T20:40:15.519Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69e7f01d19fe3cd2cdfcab4a
Added to database: 4/21/2026, 9:46:05 PM
Last enriched: 4/21/2026, 10:01:08 PM
Last updated: 4/21/2026, 11:05:57 PM
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.