← Back
CVE-2026-41695
high
CVSS 7.5
Vulnerability in org.springframework.data:spring-data-commons (CVE-2026-41695)
Summary
vulnerability in org.springframework.data:spring-data-commons (CVE-2026-41695). Risk of unauthorized operations or information disclosure. Exploitable via `GET /things`.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-41695** has been found in org.springframework.data:spring-data-commons.
Attackers can target a specific entry point like `GET /things` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "org.springframework.data:spring-data-commons CVE-2026-41695" on the vendor's site.
CVE-2026-41695 (org.springframework.data:spring-data-commons) — CWE-400 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GET /things / `computeIfAbsent` / `PathResolution.unresolved` / `InvalidPersistentPropertyPath`
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-400) exists in org.springframework.data:spring-data-commons. Attackers reach the vulnerable code path via `GET /things` without authentication.
📍 Affected scope
org.springframework.data:spring-data-commons — . Attack surface: GET /things / `computeIfAbsent` / `PathResolution.unresolved` / `InvalidPersistentPropertyPath`.
🔥 Severity
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to the patched release per vendor advisory.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual `GET /things` requests with malformed payloads or SQL meta-characters. Run `grep -r 'org.springframework.data:spring-data-commons' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'org.springframework.data:spring-data-commons' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `org.springframework.data:spring-data-commons` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'GET /things' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `GET /things` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
7Post-deployment verification verify
Replay attack against GET /things on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
org.springframework.data:spring-data-commons
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]
References
- web https://spring.io/security/cve-2026-41695
- web https://github.com/spring-projects/security-advisories/security/advisories/GHSA-88fw-v6x4-3f58
- web https://nvd.nist.gov/vuln/detail/CVE-2026-41695
- web https://github.com/spring-projects/spring-data-commons/commit/96e9475b963218bb702959524187342671f6b080
- web https://github.com/spring-projects/spring-data-commons/commit/a4f893b66c18c70f2b22f29a2b55097b73c89941
- web https://github.com/spring-projects/spring-data-commons/releases/tag/3.5.12
- web https://github.com/spring-projects/spring-data-commons/releases/tag/4.0.6
- web https://github.com/advisories/GHSA-88fw-v6x4-3f58