Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2016-8629

keycloak: user deletion via incorrect permissions check

Overview

Published
12 Mar 2018
Modified
17 Jun 2026
Medium CVE
1 Registry packages
16 OS packages
1 Linux distributions
Yes Fix available

Description

Red Hat Keycloak before version 2.4.0 did not correctly check permissions when handling service account user deletion requests sent to the rest server. An attacker with service account authentication could use this flaw to bypass normal permissions and delete users in a separate realm.

Source: OX vulnerability database

Severity

6.5 · MEDIUM

CVSS 3.0 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Weakness: CWE-284, CWE-264

Affected packages · 1

Packages affected by CVE-2016-8629
EcosystemPackageVulnerableFixed in
Maven org.keycloak:keycloak-core <2.4.0 2.4.0

Open a package to see all its vulnerabilities.

Operating systems · 8 fixes

Red Hat 1 release · 8 packages

fixed 8
rh-sso7-libunix-dbus-java rh-sso7 rh-sso7-freemarker rh-sso7-keycloak rh-sso7-zxing rh-sso7-liquibase +2
Red Hat fixes for CVE-2016-8629
ReleasePackageFixed inAdvisory
7 rh-sso7-libunix-dbus-java +1 0:0.8.0-2.jbcs.el7 RHSA-2017:0873
7 rh-sso7 +1 0:1-2.jbcs.el7 RHSA-2017:0873
7 rh-sso7-freemarker 0:2.3.23-1.redhat_2.2.jbcs.el7 RHSA-2017:0873
7 rh-sso7-keycloak +1 0:2.5.5-2.Final_redhat_1.1.jbcs.el7 RHSA-2017:0873
7 rh-sso7-zxing +2 0:3.2.1-1.redhat_4.1.jbcs.el7 RHSA-2017:0873
7 rh-sso7-liquibase +1 0:3.4.1-2.redhat_2.1.jbcs.el7 RHSA-2017:0873

2 more rows

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.