NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

CVE-2022-4492 — undertow-core

HIGHFix: undertow-io/undertow#1447

CVE-2022-4492 is a high-severity (CVSS 7.5) Server-Side Request Forgery (SSRF) vulnerability in io.undertow:undertow-core. A fix is available for io.undertow:undertow-core — see the affected versions and patch details below.

Undertow client not checking server identity presented by server certificate in https connections

Also known asGHSA-pfcc-3g6r-8rg8
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-4492.

EPSS Exploitation Probability

via FIRST.org ↗
0.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs49th percentile — riskier than 49% of all scored CVEsHighest risk
0.00%0.37%0.73%1.10%0.2%0.6%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
☕io.undertow:undertow-core☕io.undertow:undertow-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

The undertow client is not checking the server identity presented by the server certificate in https connections. This is a compulsory step (at least it should be performed by default) in https and in http/2. I would add it to any TLS client protocol.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenio.undertow:undertow-core≥ 2.3.0&&< 2.3.5.Final2.3.5.Finalio.undertow:undertow-core:2.3.5.Final
☕Mavenio.undertow:undertow-coreall versions2.2.24.Finalio.undertow:undertow-core:2.2.24.Final

Affected Products

10 products · 10 configurations
Application
build of quarkusredhat
all
Application
integration camel for spring bootredhat
all
Application
integration camel kredhat
all
Application
integration service registryredhat
all
Application
jboss enterprise application platformredhat
1 version
7.0.0
Application
jboss fuseredhat
1 version
7.0.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.undertow:undertow-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update io.undertow:undertow-core to 2.3.5.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-4492 is resolved across your whole dependency graph.

  3. Workarounds

    Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

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 HatModerate
ProductFixed inAdvisory
Migration Toolkit for Runtimes 1 on RHEL 8mtr/mtr-web-container-rhel8:1.1-8RHSA-2023:3813
MTA-6.2-RHEL-9mta/mta-operator-bundle:6.2.0-29RHSA-2023:4627
Red Hat Fuse 7.12undertowRHSA-2023:3954
Red Hat JBoss Enterprise Application Platformio.undertow/undertow-core:2.2.23.SP2-redhat-00001RHSA-2023:1516
Red Hat JBoss Enterprise Application Platform 7.1 EUS for RHEL 7eap7-glassfish-el-0:3.0.1-4.b08_redhat_00005.1.ep7.el7RHSA-2025:9582
Red Hat JBoss Enterprise Application Platform 7.3 EUS for RHEL 7eap7-jackson-annotations-0:2.10.4-3.redhat_00006.1.el7eapRHSA-2025:9583
Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 8eap7-undertow-0:2.2.23-1.SP2_redhat_00001.1.el8eapRHSA-2023:1513
Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 9eap7-undertow-0:2.2.23-1.SP2_redhat_00001.1.el9eapRHSA-2023:1514

Frequently Asked Questions

The undertow client is not checking the server identity presented by the server certificate in https connections. This is a compulsory step (at least it should be performed by default) in https and in http/2. I would add it to any TLS client protocol.
O3 Security · Impact-Aware SCA

Is CVE-2022-4492 in your dependencies?

Find it across Maven, including transitive dependencies.

CVE-2022-4492: undertow-core — Fixed in 2.3.5.Final