mTLS connection rejection via single-block CA parsing
Published Apr 21, 2026 · Updated Apr 21, 2026
Improper certificate validation in Oxia before 0.16.2 allows remote attackers to trigger rejection of mTLS connections requiring a CA chain. The trustedCertPool() function in common/security/tls.go calls pem.Decode() once and silently discards every remaining certificate block. Exposure requires a trustedCaFile containing multiple certificates; properly chained clients are then rejected as having an unknown certificate authority.
Summary
What happened
Improper certificate validation in Oxia before 0.16.2 allows remote attackers to trigger rejection of mTLS connections requiring a CA chain. The trustedCertPool() function in common/security/tls.go calls pem.Decode() once and silently discards every remaining certificate block. Exposure requires a trustedCaFile containing multiple certificates; properly chained clients are then rejected as having an unknown certificate authority.
The record
- CVE
- CVE-2026-40944
- Published
- Apr 21, 2026
- Updated
- Apr 21, 2026
- Vendor
- Oxia
- Product
- Oxia
- Classifications
- CWE-295
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 21, 2026CVE publishedPublication date reported by the CVE source.
- Apr 21, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.16.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo