CVE Intelligence
Medium

CVE-2022-22968 — Improper handling of case sensitivity in Spring Framework

In Spring Framework versions 5.3.0 - 5.3.18, 5.2.0 - 5.2.20, and older unsupported versions, the patterns for disallowedFields on a DataBinder are case sensitive which means a field is not effectively protected unless it is listed with both upper and lower case for the first character of the field, including upper and lower case for the first character of all nested fields within the property path.

Published Apr 14, 2022 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: vmware

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 5.7% (30-day exploitation probability)+14
  • Technical severity (medium)+3
  • Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
5.67%
ahead of 93% of scored CVEs · Oct 14, 2026
Affects
Netapp
Active Iq Unified Manager and 7 more
CVSS base
5.3
Medium · 2 source(s)
Prioritization reference: 7.5 provisional

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
Yes
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Maven Org.springframework:spring-context: fixed in version 5.3.19 — github.com (GitHub Security Advisories)
  • Maven Org.springframework:spring-context: fixed in version 5.2.21.RELEASE — github.com (GitHub Security Advisories)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Netapp Active Iq Unified Manager, Netapp Cloud Secure Agent, Netapp Metrocluster Tiebreaker…).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. Apply the fixed version or the patch documented under Remediation.
  4. EPSS ahead of 93% of scored CVEs: prioritize it in the patch queue.
  5. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Netapp Active Iq Unified Manager versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp Cloud Secure Agent versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp Metrocluster Tiebreaker versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp Snap Creator Framework versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp Snapmanager versions not specified by the source Vulnerable NIST National Vulnerability Database
Oracle Mysql Enterprise Monitor ≤ 8.0.29 Vulnerable NIST National Vulnerability Database
Vmware Spring Framework < 5.2.0≥ 5.2.0 and ≤ 5.2.20≥ 5.3.0 and ≤ 5.3.18 Vulnerable NIST National Vulnerability Database
Maven Org.springframework:spring-context ≥ 5.3.0 and < 5.3.19< 5.2.21.RELEASE Vulnerable GitHub Security Advisories

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
7.5 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
5.3 CVSS 3.1 Medium 3.9 1.4 nvd@nist.gov via NIST National Vulnerability Database
5.0 CVSS 2.0 Medium 10.0 2.9 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N (score shown at the top: nvd@nist.gov)
Sources disagree significantly and the divergence is under review. Every score is kept with its origin. For prioritization we use 7.5 (GitHub, Inc. via GitHub Security Advisories) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-178

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 5.67%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • Fix documented
    Oct 13, 2026 · GitHub Security Advisories
  • Affected products added · maven/org.springframework:spring-context
    Oct 13, 2026 · GitHub Security Advisories
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • CVSS changed · 5.3
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • 2022
  • CVE published
    Apr 14, 2022 · vmware

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 13, 2026 – Oct 13, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

8 on the record

Elsewhere on this site

Netapp
every CVE for this vendor
CWE-178
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-41855 Spring Framework Unsafe Deserialization via Jackson JMS Converters Jun 9, 2026
  • CVE-2026-41849 Spring Framework Denial of Service via Integer Overflow in SpEL Expressions Jun 9, 2026
  • CVE-2026-41850 Spring Framework Algorithmic Denial of Service via SpEL Expressions Jun 9, 2026
  • CVE-2026-41851 Spring Framework Denial of Service via Unbounded Cache in SpEL Jun 9, 2026
  • CVE-2026-41853 Spring Framework Multipart Request Smuggling in Spring MVC and WebFlux Jun 9, 2026
  • CVE-2026-41852 Spring Framework Arbitrary Method Invocation in SpEL Expressions Jun 9, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2022-22968 is "Improper handling of case sensitivity in Spring Framework", rated Medium. It affects Active Iq Unified Manager (Netapp); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.3 describes technical severity. EPSS 5.67% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.