How severe is CVE-2022-31679?

CVE-2022-31679 has a CVSS score of 3.7/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-31679?

CVE-2022-31679 affects the following packages: org.springframework.data:spring-data-rest-core (Maven), org.springframework.data:spring-data-rest-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-31679?

Update org.springframework.data:spring-data-rest-core to 3.6.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-31679 is resolved across your whole dependency graph.

How do I detect CVE-2022-31679 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.data:spring-data-rest-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2022-31679 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2022-31679?

O3 pinpoints whether CVE-2022-31679 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2022-31679 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-31679 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was CVE-2022-31679 published, and has it been updated?

CVE-2022-31679 was published on September 21, 2022 and was last updated on July 15, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

CVE-2022-31679

LOW

CVE-2022-31679 is a low-severity (CVSS 3.7) vulnerability in org.springframework.data:spring-data-rest-core. O3 Security confirms whether CVE-2022-31679 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Spring Data REST can expose hidden entity attributes

Also known asGHSA-fv7x-v67w-cvqv

Published

Sep 21, 2022

Updated

Jul 15, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Real-World Exposure

2 pkgs affected

☕org.springframework.data:spring-data-rest-core☕org.springframework.data:spring-data-rest-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

Applications that allow HTTP PATCH access to resources exposed by Spring Data REST in versions 3.6.0 - 3.5.5, 3.7.0 - 3.7.2, and older unsupported versions, if an attacker knows about the structure of the underlying domain model, they can craft HTTP requests that expose hidden entity attributes.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.springframework.data:spring-data-rest-core`	≥ 3.6.0&&< 3.6.7	3.6.7
☕Maven	`org.springframework.data:spring-data-rest-core`	≥ 3.7.0&&< 3.7.3	3.7.3

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.data:spring-data-rest-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.springframework.data:spring-data-rest-core to 3.6.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-31679 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2022-31679 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2022-31679. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2022-31679 in your dependencies?

O3 detects CVE-2022-31679 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works