`CVE-2021-40822` GeoServer

Affected software	GeoServer
Severity	7.5 High CVSS 3.1 2 scores
Weakness	Server-side request forgery (CWE-918)
Published	2 May 2022
Updated	13 Nov 2026

Description

GeoServer through 2.18.5 and 2.19.x through 2.19.2 allows SSRF via the option for setting a proxy host.

Exploitation status

Exploited

Real-world exploitation reported by VulnCheck KEV. CISA has not confirmed it.

CISA KEV not listed
VulnCheck KEV listed Exploitation reported in the wild. Honeypot sightings · 1 exploit · earliest 2024-01-22.
CISA Vulnrichment no assessment published
Indexed PoC 2 indexed Published artifacts you can open, in GitHub PoC, Nuclei; first seen 2022-05-17.
EPSS 19% chance in 30 days A model's forecast, not a report of exploitation. Higher than 97% of all scored CVEs.

VulnCheck KEV

Exploitation evidence from VulnCheck Known Exploited Vulnerabilities (VulnCheck KEV), used under VulnCheck's community terms. View CVE-2021-40822 in VulnCheck (free account).

Evidence	Source	Detail	Date
Honeypot sighting	Shadowserver honeypots	Exploitation attempts seen on 341 days	2024-01-22 to 2026-11-09
Exploit reference	VulnCheck XDB 7f7982a1c5d2	Exploit type: initial-access	2022-05-17

Evidence

Source

Detail

Date

Honeypot sighting

Shadowserver honeypots

Exploitation attempts seen on 341 days

2024-01-22 to 2026-11-09

Exploit reference

VulnCheck XDB 7f7982a1c5d2

Exploit type: initial-access

2022-05-17

1 of these are GitHub repositories with fewer than 5 stars. They are listed for reference and don't count toward the exploitation status above.

Index	Artifact	Stars	First seen
GitHub PoC	PoC and Dockerized vulnerable lab for CVE-2021-40822 (SSRF in GeoServer)	2	2022-05-17
Nuclei	Geoserver - Server-Side Request Forgery

Index

Artifact

Stars

First seen

GitHub PoC

PoC and Dockerized vulnerable lab for CVE-2021-40822 (SSRF in GeoServer)

2022-05-17

Nuclei

Geoserver - Server-Side Request Forgery

Waratek protection

Rule in development

Waratek is working on a rule for this CVE. No rule is available yet, and it isn't certain the rule will work.

Current target: Q2 2027 (may change)

Protection none
Action in development patch rule; current target Q2 2027, may change
Review human Researcher
Record active

Decided by	A researcher's recorded decision for this specific CVE
Finding	A researcher set this CVE's status to Rule in development, naming the ARMR SSRF rule (in development).

Decided by

A researcher's recorded decision for this specific CVE

Finding

A researcher set this CVE's status to Rule in development, naming the ARMR SSRF rule (in development).

Waratek research note

written 2026-11-13

Written by a Waratek engineer who reviewed this CVE. Their decision sets the status above, ahead of every automated rule except a withdrawal.

Comments

Rule Name: SSRF rule (in development)

Unauthenticated SSRF in GeoServer's TestWfsPost demo servlet: it fetches the address in the url request parameter and returns the response. An SSRF rule in development is meant to block an outbound request to an address taken from request parameters. Nothing blocks this CVE until that rule ships.

CVSS

7.5 HIGH v3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N 2 metrics

We show the highest score from the newest CVSS version. Scores from different versions can't be compared, and the first score listed is sometimes a 0.0 placeholder.

Version Score Band Vector Assigner Type

CVSS 3.1 7.5 HIGH CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N NVD Primary published

CVSS 2.0 5.0 none AV:N/AC:L/Au:N/C:P/I:N/A:N NVD Primary

Version	Score	Band	Vector	Assigner	Type
CVSS 3.1	7.5	HIGH	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`	NVD	Primary	published
CVSS 2.0	5.0	none	`AV:N/AC:L/Au:N/C:P/I:N/A:N`	NVD	Primary

Affected software and releases

Maven packages

Affected and fixed versions, from OSV.dev

Package	Introduced	Fixed	Last affected
`org.geoserver:gs-main`	0	none	2.18.5
`org.geoserver:gs-main`	2.19.0	none	2.19.2

Products and versions

2 products, 4 version entries

Source	Vendor	Product	Scheme	Affected versions
osv	org.geoserver	gs-main	generic	≤ 2.18.5 · ≥ 2.19.0 and ≤ 2.19.2
nvd	osgeo	geoserver	generic	≤ 2.18.5 · ≥ 2.19.0 and ＜ 2.19.3

Source

Vendor

Product

Scheme

Affected versions

osv

org.geoserver

gs-main

generic

≤ 2.18.5 · ≥ 2.19.0 and ≤ 2.19.2

nvd

osgeo

geoserver

generic

≤ 2.18.5 · ≥ 2.19.0 and ＜ 2.19.3

References

URL	Tags
https://github.com/geoserver/geoserver	PACKAGE
https://github.com/geoserver/geoserver/compare/2.19.2...2.19.3	WEB
https://github.com/geoserver/geoserver/releases	WEB
https://osgeo-org.atlassian.net/browse/GEOS-10229	WEB
https://osgeo-org.atlassian.net/browse/GEOS-10229?focusedCommentId=83508	WEB

URL

Timeline

Published	2022-05-02	By the CVE Program.
VulnCheck KEV: earliest evidence	2024-01-22	Date of the oldest evidence of exploitation in VulnCheck KEV's record. VulnCheck does not publish the date it listed the CVE.
NVD record modified	2026-06-17	NVD's own last-modified date for this record.
VulnCheck KEV: latest evidence	2026-11-09	Date of the newest report, exploit reference or honeypot sighting in VulnCheck KEV's record.
Classification created	2026-11-13	First commit adding this CVE's research note.
Last VRT activity	2026-11-13	Most recent commit touching this CVE's classification, patch or rule file.

Published

2022-05-02

By the CVE Program.

VulnCheck KEV: earliest evidence

2024-01-22

Date of the oldest evidence of exploitation in VulnCheck KEV's record. VulnCheck does not publish the date it listed the CVE.

NVD record modified

2026-06-17

NVD's own last-modified date for this record.

VulnCheck KEV: latest evidence

2026-11-09

Date of the newest report, exploit reference or honeypot sighting in VulnCheck KEV's record.

Classification created

2026-11-13

First commit adding this CVE's research note.

Last VRT activity

2026-11-13

Most recent commit touching this CVE's classification, patch or rule file.

How VRT decided (4 of 24 rules ran)

4 of 24 rules ran. The rest didn't run because an earlier rule had already settled the CVE.

# Rule Outcome Status Detail

identity: Does this identifier describe a vulnerability at all? the first rule that matches decides

1 rejected no match CVE Program withdrawal of this identifier

scope: Is it a vulnerability Waratek protects? the first rule that matches decides

2 armr-patch-file no match An ARMR patch file on disk for this CVE

3 armr-secure-rule-file no match An ARMR security-rule template on disk for this CVE

4 manual-classification decided it matched Rule in development A researcher set this CVE's status to Rule in development, naming the ARMR SSRF rule (in development).

5 manual classification not reached Manual classification of this CVE in the legacy dataset

6 non-java-upstream not reached A root cause in non-Java code: an OS kernel, a C library, or a bundled runtime

7 oracle-component not reached The defect being in a component of a tracked product the agent does not reach: JavaFX, the Java SE installer, the JInitiator browser plug-in, the native WebLogic proxy plug-in, or a native part of Oracle Application Server or Collaboration Suite (HTTP Server, Web Cache, Internet Directory, mail and calendar servers). Oracle gives these no CPE of their own and names them only in the description.

8 java-client-side not reached Oracle's own risk-matrix note saying the CVE is reached only through untrusted code in the Java sandbox (applets, Web Start) or only through a client installation of Java, so a server running its own trusted code is not exposed

9 osv-maven not reached An OSV.dev record of this CVE affecting a package published to Maven Central. When every such package is one business applications do not use (Minecraft mods and launchers, Fastjson) and no tracked product is named by CPE, it settles the CVE as Outside Waratek scope instead

10 cna-maven-package not reached An affected Maven artifact named by the CNA itself

11 known-cpe-product not reached An NVD CPE naming a product ARMR tracks

12 cna-cpe-product not reached A CPE the CNA published naming a tracked product. Oracle publishes these on advisory day, months before NVD.

13 oracle-advisory-family not reached A tracked product family named in Oracle's own risk matrix. CPE cannot carry a suite name, only a module.

14 cna-named-product not reached A tracked product named in words by the CVE's own CNA, on a record with no CPE yet. Apache and Eclipse publish these on advisory day, before NVD adds CPE data.

15 non-deployable-product not reached The only affected product being a sealed appliance image, where Java runs but no -javaagent can be attached

16 unmatched-product not reached No tracked product matched above, and none present at all

disposition: What do we do about one that is? every rule runs

17 patch-hint not reached A reference pointing at the upstream fix: a commit, a PR, a Red Hat bug

18 open-source-maven not reached The affected package being open source on Maven, so the fix can be read

19 poc-derivable not reached An indexed exploit clearing the evidence bar to reverse-engineer, where there is no source to read

20 no-exploit not reached Nothing to build a rule from yet: no published exploit, no CISA record of exploitation and no source-level change to read

21 secure-rule-match not reached A vulnerability class already blocked by an ARMR security rule

22 exploited-no-fix-or-poc not reached Somebody exploiting this CVE (a CISA or VulnCheck KEV listing, or a CISA verdict of active exploitation), with no fix, source code or PoC to build a rule from

23 below-action-threshold not reached Medium or Low severity, no CISA or VulnCheck KEV listing, no PoC clearing the evidence bar, no CISA verdict, no Oracle advisory

24 no-exploit-published not reached Exploit code for this candidate, published in a reviewed catalogue or a GitHub repository with 5 or more stars, or in use per CISA or VulnCheck; not only a CISA verdict, a forecast, or nothing at all

NVD ↗ · CVE.org ↗