A flaw was found in cluster-network-operator. The OVN IPsec certificate signer does not verify that the requested certificate Subject and DNS names belong to the requesting node. An attacker with an accepted OVN node credential and permission to submit certificate signing requests could obtain a signed certificate identifying another node. In certificate authenticated OVN IPsec deployments, this could enable peer impersonation when the attacker can also satisfy the configured peer address check, potentially compromising protected traffic.
Severity
CVSS 3.1
5.9 medium
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N
EPSS
0.3% estimated probability of exploitation activity in the next 30 days; 23rd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-20. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
Show the promptExplain CVE-2026-133531 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-133531?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-133531?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-133531 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.