How severe is GHSA-jh7q-5mwf-qvhw?

GHSA-jh7q-5mwf-qvhw has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-jh7q-5mwf-qvhw?

GHSA-jh7q-5mwf-qvhw affects the following packages: org.keycloak:keycloak-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-jh7q-5mwf-qvhw?

Update org.keycloak:keycloak-core to version 13.0.0 or later. Run your dependency manager's update command and verify no transitive dependencies pin the vulnerable version. Use O3 Security's SCA scanner to confirm the fix is applied across your entire dependency tree.

Is GHSA-jh7q-5mwf-qvhw actively exploited in the wild?

Yes. There are 4 known exploit references for GHSA-jh7q-5mwf-qvhw, including 1 documented proof-of-concept exploit on Exploit-DB and 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-jh7q-5mwf-qvhw?

GHSA-jh7q-5mwf-qvhw has an EPSS (Exploit Prediction Scoring System) score of 92.3%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is GHSA-jh7q-5mwf-qvhw?

GHSA-jh7q-5mwf-qvhw is classified as Server-Side Request Forgery (SSRF) (CWE-918). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for GHSA-jh7q-5mwf-qvhw?

A Nuclei detection template exists for GHSA-jh7q-5mwf-qvhw, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-jh7q-5mwf-qvhw published, and has it been updated?

GHSA-jh7q-5mwf-qvhw was published on May 24, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

GHSA-jh7q-5mwf-qvhw

MEDIUM

Keycloak vulnerable to Server-Side Request Forgery

Also known asCVE-2020-10770

Published

May 24, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

4 known

EPSS Exploitation Probability

via FIRST.org ↗

92.3%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

☕org.keycloak:keycloak-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

A 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 request_uri. This flaw allows an attacker to use this parameter to execute a Server-side request forgery (SSRF) attack.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.keycloak:keycloak-core`	all versions	13.0.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-50405webappsjava

Keycloak 12.0.1 - 'request_uri ' Blind Server-Side Request Forgery (SSRF) (Unauthenticated)

by Mayank Deshmukh · Oct 13, 2021

Exploit-DB Source

Frequently Asked Questions

A 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 `request_uri`. This flaw allows an attacker to use this parameter to execute a Server-side request forgery (SSRF) attack.

O3 Security · Impact-Aware SCA

Is GHSA-jh7q-5mwf-qvhw in your stack?

O3 detects GHSA-jh7q-5mwf-qvhw across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works

CVSS Score

5.3/10

CVSS v3 base score

Vector breakdown

AV:Attack Vector

Network

AC:Attack Complexity

Low

PR:Privileges Required

None

UI:User Interaction

None

S:Scope

Unchanged

C:Confidentiality

None

I:Integrity

Low

A:Availability

None

Raw vector

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

CWE Classification

CWE-918Server-Side Request Forgery (SSRF)

Weaponization

OpenSSF Scorecard

Package health score

keycloak-documentation

3.9/10

Code-Review9/10

Maintained0/10

Branch-ProtectionN/A

Assessed Jun 8, 2026

Timeline

First exploit

Oct 13, 2021

Disclosed

May 24, 2022

Last updated

Nov 8, 2023

Identifiers

GHSA-jh7q-5mwf-qvhw

References

Advisorynvd.nist.gov Webgithub.com Webgithub.com Webbugzilla.redhat.com Webissues.redhat.com Webissues.redhat.com Webpacketstormsecurity.com Packagegithub.com

Data from OSV.dev, enriched by O3 Security. Refreshed hourly.