Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-7jrq-q4pq-rhm6

Oxia's TLS CA certificate chain validation fails with multi-certificate PEM bundles

CVSS 6.9 MediumEPSS 0.0016 · 5th percentile

Published by the GitHub Advisory Database at 14 Apr 2026, 23:15 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/oxia-db/oxiaGo<0.16.20.16.2
Identifiers
GHSA-7jrq-q4pq-rhm6 · CVE-2026-40944 · GO-2026-5226
Weakness (CWE)
CWE-295
Tags
Published
14 Apr 2026
Updated
25 Jun 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Oxia's TLS configuration (github.com/oxia-db/oxia) before 0.16.2 loads only the first certificate from a trusted CA file, so CA bundles containing intermediate and root certificates are not fully loaded. As a result, clients with properly chained certificates are rejected during mTLS, and operators may be pushed to weaken client certificate verification. The source gives few details on attacker requirements. Upgrade to 0.16.2 or later. As a workaround, use CA files that contain only the single certificate that directly issues client certificates.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.9 Medium 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0016, the 5th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:07 UTC First seen by agentprime
  2. 31 Oct 2026, 15:07 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.