CVE-2026-40944

Home/CVE/Oxia is a metadata store and coordination system. Prior to 0.16.2, the trustedCertPool() function in the TLS configurati

CVE

↯ PDF report Light Dark

Oxia is a metadata store and coordination system. Prior to 0.16.2, the trustedCertPool() function in the TLS configurati

Oxia is a metadata store and coordination system. Prior to 0.16.2, the trustedCertPool() function in the TLS configuration only parses the first PEM block from CA certificate files. When a CA bundle contains multiple certificates (e.g., intermediate + root CA), only the first certificate is loaded.

This silently breaks certificate chain validation for mTLS. This vulnerability is fixed in 0.16.2.

EPSS 0.00033

EPSS exploitation odds0.03% · top 89%

Schedule remediation

SSVC automatable: yes - attacks can be scripted at scale
⚠ NVD has not scored this CVE yet - manual triage required (common for recent CVEs)

Sigma rules0 YARA rules0

Look this up elsewhere - one-click external pivots

NVD CVE.org CISA Exploit-DB GitHub PoC VulnCheck KEV GreyNoise

▸ How to read a CVE - triage first, then detect and patch

This page is every public fact about CVE-2026-40944, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.

Triage: should I act now? Four signals, and they are not interchangeable:

CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked. EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal. CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score. Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.

How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.

Then what - two workflows:

Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits. PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.

Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).

▣

Severity & exploitation scoring

EPSS exploitation probability

0.03%

Top 89%odds of exploitation in the next 30 days

SSVC triage · cisa-vulnrichment

Exploitation

none

Automatable

yes

Tech impact

partial

Lifecycle

21 Apr 2026Published to NVD
22 Apr 2026Last modified

Every entry is a recorded date - NVD publish/modify, CISA KEV add, public exploit disclosure. No inferred events.

▤

CAPEC attack patterns

Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.

CAPEC-CAPEC-459 · Creating a Rogue Certification Authority Certificate CAPEC-CAPEC-475 · Signature Spoofing by Improper Validation

⬡

Weakness Classification

CWE-295Improper Certificate Validation

▤

Affected Packages

Language-ecosystem packages (from OSV) tied to this CVE, with the version that fixes it - the dependency-level detail NVD doesn’t carry.

Go github.com/oxia-db/oxia HIGH fixed in 0.16.2

▤

Related CVEs

CVEs linked to this one by a shared weakness (CWE) or affected product - joins on data already in the engine, with the reason shown per row. Not a guess.

CVE-2002-0862 The (1) CertGetCertificateChain, (2) CertVerifyCertificateChainPolicy, and (3) W... same CWE-295 CVE-2003-1229 X509TrustManager in (1) Java Secure Socket Extension (JSSE) in SDK and JRE 1.4.0... same CWE-295 CVE-2005-3170 The LDAP client on Microsoft Windows 2000 before Update Rollup 1 for SP4 accepts... same CWE-295 MEDIUM CVE-2006-7246 NetworkManager 0.9.x does not pin a certificate's subject to an ESSID when 802.1... same CWE-295 MEDIUM

🔗

References & Sources

Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.

https://github.com/oxia-db/oxia/security/advisories/GHSA-7jrq-q4pq-rhm6