Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-22741: Spring MVC and WebFlux applications are vulnerable to cache poisoning when resolving static resources. More

14
Routine
LOW 3.1UPGRADE

CVE-2026-22741 is a low-severity flaw (CVSS 3.1) affecting spring framework. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Spring MVC and WebFlux applications are vulnerable to cache poisoning when resolving static resources. More precisely, an application can be vulnerable when all the following are true: * the application is using Spring MVC or Spring WebFlux * the application is configuring the  resource chain support https://docs.spring.io/spring-framework/reference/web/webmvc/mvc-config/static-resources.html#page-title  with caching enabled * the app

Why this priority

  • No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score3.1 (Low)
Attack vectorNetwork (remote)
Attack complexityHigh
Privileges neededNone
User interactionRequired
EPSS exploit chance0.2% (top 86%)
CISA exploited listNo
WeaknessCWE-524
Published2026-04-29
Last modified2026-10-26
Publisher (CNA): VMware · Vendor: vmware

Share: LinkedIn · X · Reddit

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

vmware spring framework UPGRADE
Affected: < 5.3.48 · >= 6.1.0 and < 6.1.27 · >= 6.2.0 and < 6.2.18 · >= 7.0.0 and < 7.0.7
Fixed in: 5.3.48, 6.1.27, 6.2.18, 7.0.7
Safe to downgrade to: a release before 6.1.0
1. Check installed version
apt-cache policy spring-framework || rpm -q spring-framework || spring-framework --version
2. UPGRADE to 5.3.48 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade spring-framework
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade spring-framework
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 6.1.0 (Debian / Ubuntu)
apt-cache madison spring-framework sudo apt install spring-framework=<VERSION_BEFORE_6.1.0> sudo apt-mark hold spring-framework
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list spring-framework sudo dnf downgrade spring-framework-<VERSION_BEFORE_6.1.0> sudo dnf versionlock add spring-framework
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-22741?

spring framework: upgrade to 5.3.48, 6.1.27, 6.2.18, 7.0.7. Exact commands for each OS are on this page.

Is CVE-2026-22741 being exploited?

CVE-2026-22741 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-22741 affect?

CVE-2026-22741 affects spring framework. Severity is low (CVSS 3.1). Spring MVC and WebFlux applications are vulnerable to cache poisoning when resolving static resources. More precisely, an application can be vulnerable when all the following are true: * the application is using Spring MVC or Spring W

How urgent is CVE-2026-22741?

Priority 14/100. No elevated risk signals yet.

Software pages

Spring Framework vulnerabilities · VMware vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.