Skip to main content
Menu
CVEs

Red Hat signature bypass in SAML logout requests

CVE-2026-133430Published November 19, 2026, updated

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

Summary

Keycloak SAML components in Red Hat Build of Keycloak, Red Hat Single Sign-On 7, and Red Hat JBoss Enterprise Application Platform accept unsigned SAML logout requests that contain any validly signed assertion. A remote attacker with a low-privilege login can embed a signed assertion into a forged logout request, which terminates other users' active sessions and causes a denial of service.

Written by a model

Original description

A flaw was found in Keycloak. This vulnerability allows an authenticated remote attacker to cause a denial of service by terminating active sessions of arbitrary users. When processing Security Assertion Markup Language (SAML) documents that lack a root signature, Keycloak accepts the request as long as any assertion within the document is signed, without verifying its context or placement. An attacker holding a validly signed assertion can embed it into an unsigned logout request for another user, causing Keycloak to accept the forged request and terminate the victim's session.

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-133430 (Keycloak: org.keycloak:keycloak-saml-adapter-core: org.keycloak:keycloak-saml-core: saml logoutrequest signature validation accepts a…), 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-133430 (entry last updated 2026-11-19):
Affected:
- Red Hat Red Hat Build of Keycloak: version range not reported
- Red Hat Red Hat Build of Keycloak: version range not reported
- Red Hat Red Hat JBoss Enterprise Application Platform 7: version range not reported
- Red Hat Red Hat JBoss Enterprise Application Platform 7: version range not reported
- Red Hat Red Hat JBoss Enterprise Application Platform 7: version range not reported
- Red Hat Red Hat JBoss Enterprise Application Platform 8: version range not reported
- Red Hat Red Hat JBoss Enterprise Application Platform Expansion Pack: version range not reported
- Red Hat Red Hat Single Sign-On 7: version range not reported
- Red Hat Red Hat Single Sign-On 7: 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-133430 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133430 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=2577265
- https://access.redhat.com/security/cve/CVE-2026-133430
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-133430
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-133430"}.

Affected versions

cve.now Index

23Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach10/20Shipped in major Linux distributions
  • Severity5.4/10CVSS 5.4
  • No patch5/5No fixed version listed; see vendor advisory

What would change the score

  • Would score about 78 if added to CISA KEV
  • Would score about 73 if CISA's SSVC rates exploitation active
  • Would score about 42 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 4

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

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