Skip to main content
Menu
CVEs

Red Hat authorization bypass in IPsec certificate signer

CVE-2026-133531EUVD-2026-131356GHSA-9RHX-M7G8-6Q4VPublished November 20, 2026, updated

5.9MediumCNA
Exploited
No known exploitation
Fix
See vendor advisory
Who is exposed
Not reported

Summary

Red Hat OpenShift Container Platform and Red Hat OpenShift Virtualization contain a flaw in the cluster-network-operator IPsec certificate signer, which does not check that requested certificate names belong to the requesting node. A remote attacker who already holds an OVN node credential and permission to submit certificate signing requests could obtain a certificate identifying another node, enabling peer impersonation and potentially compromising protected traffic in certificate-authenticated OVN IPsec deployments.

Written by a model

Original description

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.

What to do

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-133531 (Cluster-network-operator: cluster-network-operator: ipsec signer fails to bind certificate identity to the requesting node), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-133531 (entry last updated 2026-11-20):
Affected:
- Red Hat Red Hat OpenShift Container Platform 4: version range not reported
- Red Hat Red Hat OpenShift Container Platform 4: version range not reported
- Red Hat Red Hat OpenShift Container Platform 4: version range not reported
- Red Hat Red Hat OpenShift Container Platform 4: version range not reported
- Red Hat Red Hat OpenShift Container Platform 4: version range not reported
- Red Hat Red Hat OpenShift Container Platform 4: version range not reported
- Red Hat Red Hat OpenShift Container Platform 5: version range not reported
- Red Hat Red Hat OpenShift Virtualization 4: version range not reported
- Red Hat Red Hat OpenShift Virtualization 4: version range not reported
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133531 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133531 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://bugzilla.redhat.com/show_bug.cgi?id=2577526
- https://access.redhat.com/security/cve/CVE-2026-133531
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-133531
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133531"}.

Affected versions

cve.now Index

25Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach10/20Shipped in major Linux distributions
  • Severity6.9/10CVSS 5.9, total technical impact per CISA
  • No patch5/5No fixed version listed; see vendor advisory

What would change the score

  • Would score about 80 if added to CISA KEV
  • Would score about 75 if CISA's SSVC rates exploitation active
  • Would score about 44 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  4. Record last updated

Evidence 4

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-133531
RecordNVD · CVE-2026-133531
Write-ups 1Establishes: Technical detail and context.
Reportbugzilla.redhat.com · show_bug.cgi?id=2577526
Other links 1
Linkaccess.redhat.com · security/cve/CVE-2026-133531

No corrections so far. Something wrong on this page? Report an error.