Authenticated policy bypass via unsigned JWT header
Published Jul 17, 2026 · Updated Jul 17, 2026
Authentication bypass in Red Hat Keycloak-based products allows remote authenticated users to evade required signed-JWT client assertions. SecureSigningAlgorithmForSignedJwtExecutor trusts the alg field in a raw assertion header without verifying an assertion type or assertion-based authenticator. Valid client credentials and an enabled signed-JWT client policy are required; exploitation permits authentication or client updates without the mandated cryptographic proof.
Summary
What happened
Authentication bypass in Red Hat Keycloak-based products allows remote authenticated users to evade required signed-JWT client assertions. SecureSigningAlgorithmForSignedJwtExecutor trusts the alg field in a raw assertion header without verifying an assertion type or assertion-based authenticator. Valid client credentials and an enabled signed-JWT client policy are required; exploitation permits authentication or client updates without the mandated cryptographic proof.
The record
- CVE
- CVE-2026-16093
- Published
- Jul 17, 2026
- Updated
- Jul 17, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat JBoss Enterprise Application Platform Expansion Pack
- Classifications
- CWE-807, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 17, 2026CVE publishedPublication date reported by the CVE source.
- Jul 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo