Skip to content
Noroxi
NVD / CVE Program· CNA redhat

CVE-2016-8629: Red Hat Keycloak before version 2.4.0 did not correctly check permissions when handling service account user deletion requests sent to the…

MediumCVSS 6.5 · v3.0—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 27/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1.9% (FIRST EPSS); higher than 80% of all records.
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: org.keycloak:keycloak-core (Maven) 2.4.0; rh-sso7 (Red Hat:red_hat_single_sign_on:7::el6) 0:1-2.jbcs.el6; rh-sso7-freemarker (Red Hat:red_hat_single_sign_on:7::el6) 0:2.3.23-1.redhat_2.2.jbcs.el6.

Low priority for now. Upgrade to org.keycloak:keycloak-core (Maven) 2.4.0; rh-sso7 (Red Hat:red_hat_single_sign_on:7::el6) 0:1-2.jbcs.el6; rh-sso7-freemarker (Red Hat:red_hat_single_sign_on:7::el6) 0:2.3.23-1.redhat_2.2.jbcs.el6 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Mar 12, 2018
Updated
Jun 16, 2026
EPSS
1.9% · 80th percentile

Report tools

JSON

Action score

27

Monitor

Low priority for now.

CVSS
26 / 40 · 6.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 1.9%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2016-8629

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
redhatkeycloak
redhatsingle sign on
redhatenterprise linux server

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

  • Red Hat, Inc. Keycloak

    • 2.4.0affected

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • redhat keycloakbefore 2.4.0
  • redhat single sign on7.1
  • redhat single sign on7.2

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Mavenorg.keycloak:keycloak-corebefore 2.4.02.4.0
Red Hat:red_hat_single_sign_on:7::el6rh-sso7before 0:1-2.jbcs.el60:1-2.jbcs.el6
Red Hat:red_hat_single_sign_on:7::el6rh-sso7-freemarkerbefore 0:2.3.23-1.redhat_2.2.jbcs.el60:2.3.23-1.redhat_2.2.jbcs.el6
Red Hat:red_hat_single_sign_on:7::el6rh-sso7-javapackages-toolsbefore 0:3.4.1-5.15.3.jbcs.el60:3.4.1-5.15.3.jbcs.el6
Red Hat:red_hat_single_sign_on:7::el6rh-sso7-keycloakbefore 0:2.5.5-2.Final_redhat_1.1.jbcs.el60:2.5.5-2.Final_redhat_1.1.jbcs.el6
Red Hat:red_hat_single_sign_on:7::el6rh-sso7-keycloak-serverbefore 0:2.5.5-2.Final_redhat_1.1.jbcs.el60:2.5.5-2.Final_redhat_1.1.jbcs.el6
Red Hat:red_hat_single_sign_on:7::el6rh-sso7-libunix-dbus-javabefore 0:0.8.0-2.jbcs.el60:0.8.0-2.jbcs.el6
Red Hat:red_hat_single_sign_on:7::el6rh-sso7-libunix-dbus-java-debuginfobefore 0:0.8.0-2.jbcs.el60:0.8.0-2.jbcs.el6
Red Hat:red_hat_single_sign_on:7::el6rh-sso7-libunix-dbus-java-develbefore 0:0.8.0-2.jbcs.el60:0.8.0-2.jbcs.el6
Red Hat:red_hat_single_sign_on:7::el6rh-sso7-liquibasebefore 0:3.4.1-2.redhat_2.1.jbcs.el60:3.4.1-2.redhat_2.1.jbcs.el6
Red Hat:red_hat_single_sign_on:7::el6rh-sso7-liquibase-corebefore 0:3.4.1-2.redhat_2.1.jbcs.el60:3.4.1-2.redhat_2.1.jbcs.el6
Red Hat:red_hat_single_sign_on:7::el6rh-sso7-python-javapackagesbefore 0:3.4.1-5.15.3.jbcs.el60:3.4.1-5.15.3.jbcs.el6
Red Hat:red_hat_single_sign_on:7::el6rh-sso7-runtimebefore 0:1-2.jbcs.el60:1-2.jbcs.el6
Red Hat:red_hat_single_sign_on:7::el6rh-sso7-twitter4jbefore 0:4.0.4-1.redhat_3.1.jbcs.el60:4.0.4-1.redhat_3.1.jbcs.el6
Red Hat:red_hat_single_sign_on:7::el6rh-sso7-twitter4j-corebefore 0:4.0.4-1.redhat_3.1.jbcs.el60:4.0.4-1.redhat_3.1.jbcs.el6
Red Hat:red_hat_single_sign_on:7::el6rh-sso7-zxingbefore 0:3.2.1-1.redhat_4.1.jbcs.el60:3.2.1-1.redhat_4.1.jbcs.el6
Red Hat:red_hat_single_sign_on:7::el6rh-sso7-zxing-corebefore 0:3.2.1-1.redhat_4.1.jbcs.el60:3.2.1-1.redhat_4.1.jbcs.el6
Red Hat:red_hat_single_sign_on:7::el6rh-sso7-zxing-javasebefore 0:3.2.1-1.redhat_4.1.jbcs.el60:3.2.1-1.redhat_4.1.jbcs.el6
Red Hat:red_hat_single_sign_on:7::el7rh-sso7before 0:1-2.jbcs.el70:1-2.jbcs.el7
Red Hat:red_hat_single_sign_on:7::el7rh-sso7-freemarkerbefore 0:2.3.23-1.redhat_2.2.jbcs.el70:2.3.23-1.redhat_2.2.jbcs.el7
Red Hat:red_hat_single_sign_on:7::el7rh-sso7-javapackages-toolsbefore 0:3.4.1-5.15.3.jbcs.el70:3.4.1-5.15.3.jbcs.el7
Red Hat:red_hat_single_sign_on:7::el7rh-sso7-keycloakbefore 0:2.5.5-2.Final_redhat_1.1.jbcs.el70:2.5.5-2.Final_redhat_1.1.jbcs.el7
Red Hat:red_hat_single_sign_on:7::el7rh-sso7-keycloak-serverbefore 0:2.5.5-2.Final_redhat_1.1.jbcs.el70:2.5.5-2.Final_redhat_1.1.jbcs.el7
Red Hat:red_hat_single_sign_on:7::el7rh-sso7-libunix-dbus-javabefore 0:0.8.0-2.jbcs.el70:0.8.0-2.jbcs.el7

+11

Other highest-scoring records for the same primary product.

  • CVE-2020-10770A flaw was found in Keycloak before 13.0.0, where it is possible to force the server to call out an unverified URL using the OIDC parameter…
    42Plan
  • CVE-2022-1245A privilege escalation flaw was found in the token exchange feature of keycloak.
    39Monitor
  • CVE-2019-14910A vulnerability was found in keycloak 7.x, when keycloak is configured with LDAP user federation and StartTLS is used instead of SSL/TLS…
    39Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2017-12160Oct 26, 2017 · It was found that Keycloak oauth would permit an authenticated resource to obtain an access/refresh token pair from the authentication…
    29Monitor
  • Later →CVE-2017-2585Mar 12, 2018 · Red Hat Keycloak before version 2.5.1 has an implementation of HMAC verification for JWS tokens that uses a method that runs in…
    24Monitor
  • Later →CVE-2018-10912Jul 23, 2018 · keycloak before version 4.0.0.final is vulnerable to a infinite loop in session replacement.
    19Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Maven:org.keycloak:keycloak-core2.4.0Package registry (OSV)
red hat:rh-sso70:1-2.jbcs.el6 · Red Hat:red_hat_single_sign_on:7::el6Package registry (OSV)
red hat:rh-sso7-freemarker0:2.3.23-1.redhat_2.2.jbcs.el6 · Red Hat:red_hat_single_sign_on:7::el6Package registry (OSV)
red hat:rh-sso7-javapackages-tools0:3.4.1-5.15.3.jbcs.el6 · Red Hat:red_hat_single_sign_on:7::el6Package registry (OSV)
red hat:rh-sso7-keycloak0:2.5.5-2.Final_redhat_1.1.jbcs.el6 · Red Hat:red_hat_single_sign_on:7::el6Package registry (OSV)
red hat:rh-sso7-keycloak-server0:2.5.5-2.Final_redhat_1.1.jbcs.el6 · Red Hat:red_hat_single_sign_on:7::el6Package registry (OSV)
red hat:rh-sso7-libunix-dbus-java0:0.8.0-2.jbcs.el6 · Red Hat:red_hat_single_sign_on:7::el6Package registry (OSV)
red hat:rh-sso7-libunix-dbus-java-debuginfo0:0.8.0-2.jbcs.el6 · Red Hat:red_hat_single_sign_on:7::el6Package registry (OSV)
red hat:rh-sso7-libunix-dbus-java-devel0:0.8.0-2.jbcs.el6 · Red Hat:red_hat_single_sign_on:7::el6Package registry (OSV)
red hat:rh-sso7-liquibase0:3.4.1-2.redhat_2.1.jbcs.el6 · Red Hat:red_hat_single_sign_on:7::el6Package registry (OSV)
red hat:rh-sso7-liquibase-core0:3.4.1-2.redhat_2.1.jbcs.el6 · Red Hat:red_hat_single_sign_on:7::el6Package registry (OSV)
red hat:rh-sso7-python-javapackages0:3.4.1-5.15.3.jbcs.el6 · Red Hat:red_hat_single_sign_on:7::el6Package registry (OSV)
red hat:rh-sso7-runtime0:1-2.jbcs.el6 · Red Hat:red_hat_single_sign_on:7::el6Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
high · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
High
Availability impact
None

CVSS vector

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

nvd-primary

References

All records