Security readout for executives and security teams
Plain-English summary
Keycloak’s Docker registry login path may still issue tokens for a Docker registry client after an administrator disables that client. Disabling the client is therefore not a complete access cutoff for that protocol. Business impact is limited but real: users with existing valid credentials may retain unintended access to container registry resources.
Executive priority
Treat as a targeted low-severity access-control issue. Prioritize remediation where Keycloak protects container registries or where client disablement is used for offboarding, incident response, or emergency access revocation. It is not currently supported as an actively exploited emergency.
Technical view
CVE-2026-2733 is a CWE-285 authorization flaw in Keycloak’s Docker v2 authentication endpoint. The endpoint does not fully enforce the disabled state of a Docker registry client, allowing token issuance using previously valid credentials. Red Hat rates it Low, CVSS 3.1 score 3.8, with network access, low complexity, and high privileges required.
Likely exposure
Exposure is most likely where affected Red Hat Keycloak-related products are used for Docker registry authentication and administrators rely on disabling registry clients to revoke access. Listed affected products include Red Hat Build of Keycloak, Red Hat Single Sign-On 7, JBoss EAP 8, and EAP Expansion Pack packages containing keycloak-services.
Exploitation context
No active exploitation is indicated in the provided sources, and the CVE is not listed as KEV. Abuse requires previously valid credentials and high privileges per the CVSS vector. The main risk is administrative intent being bypassed when a disabled Docker registry client can still receive tokens.
Researcher notes
The key behavior to validate is enforcement of the client enabled flag on the Docker v2 authentication endpoint. Evidence identifies continued token issuance after administrative disablement. The source bundle names affected Red Hat products and advisories, but detailed upstream commit or complete fixed-version mapping is not provided here.
Mitigation direction
- Review Red Hat advisories RHSA-2026:3947 and RHSA-2026:3948 for applicable updates.
- Apply vendor-provided updates or guidance for affected Red Hat Keycloak-related packages.
- Do not rely solely on disabling a Docker registry client until remediated.
- Review access controls for container registries using Keycloak Docker v2 authentication.
Validation and detection
- Inventory Keycloak, Red Hat SSO, JBoss EAP, and Expansion Pack deployments using keycloak-services.
- Identify Docker registry clients configured in Keycloak realms.
- Confirm whether affected package versions match Red Hat’s CVE and errata records.
- After remediation, verify disabled Docker registry clients no longer receive tokens.
- Review logs for token issuance to clients disabled before patching.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-285: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-2733 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Low
- CVSS
- 3.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N1.22.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
3.8LowVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- RHSA-2026:3947CVE reference · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:3948CVE reference · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/security/cve/CVE-2026-2733CVE reference · vdb-entry, x_refsource_REDHAT
- RHBZ#2440895CVE reference · issue-tracking, x_refsource_REDHAT
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Authorization
Improper Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.