# CVE-2020-1698: keycloak-core — Fixed in 9.0.0

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

# CVE-2020-1698 — keycloak-core

MEDIUM [Fix: keycloak/keycloak#6751](https://github.com/keycloak/keycloak/pull/6751)

CVE-2020-1698 is a medium-severity (CVSS 5.5) Information Exposure vulnerability in org.keycloak:keycloak-core. A fix is available for org.keycloak:keycloak-core — see the affected versions and patch details below.

Keycloak leaks sensitive information in logged exceptions

Also known as[GHSA-qgmm-f2qw-r95f](/vulnerability/GHSA-qgmm-f2qw-r95f)

Published

May 11, 2020

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

## EPSS Exploitation Probability

[via FIRST.org ↗](https://www.first.org/epss/)

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs31th percentile — riskier than 31% of all scored CVEsHighest risk

0.00%0.29%0.58%0.87%0.1%0.4%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/).

## How urgent is this, really

## Where this sits among everything scored

## Real-World Exposure

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 in versions before 9.0.0. A logged exception in the HttpMethod class may leak the password given as parameter. The highest threat from this vulnerability is to data confidentiality.

## Affected Packages

1 total 1 fixed

Ecosystem

Package

Vulnerable range

Fix

☕Maven

`org.keycloak:keycloak-core` 

all versions

9.0.0`org.keycloak:keycloak-core:9.0.0`

## Affected Products

1 product · 1 configurations

Application

`keycloak`redhat

< 9.0.0

range

## Detection & mitigation playbook

Open-source dependency

1.  ### Detect
    
    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.keycloak:keycloak-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
    
2.  ### Fix
    
    Update org.keycloak:keycloak-core to 9.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-1698 is resolved across your whole dependency graph.
    
3.  ### Workarounds
    
    Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
    

## Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatLow

Product

Fixed in

Advisory

Red Hat Runtimes Spring Boot 2.2.6

`keycloak-core`

[RHSA-2020:2252](https://access.redhat.com/errata/RHSA-2020:2252)

Red Hat Single Sign-On 7.4.0

see advisory

[RHSA-2020:5625](https://access.redhat.com/errata/RHSA-2020:5625)

Text-Only RHOAR

see advisory

[RHSA-2020:2905](https://access.redhat.com/errata/RHSA-2020:2905)

## Frequently Asked Questions

A flaw was found in keycloak in versions before 9.0.0. A logged exception in the HttpMethod class may leak the password given as parameter. The highest threat from this vulnerability is to data confidentiality.

O3 Security · Impact-Aware SCA

### Is CVE-2020-1698 in your dependencies?

Find it across Maven, including transitive dependencies.

[Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)