Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-8r2h-xh92-gq57

Spring Data Relational: Attackers can supply wildcard characters to perform boolean-based blind data inference

CVSS 4.8 MediumEPSS 0.0023 · 13th percentile

Published by the GitHub Advisory Database at 10 Jun 2026, 00:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.springframework.data:spring-data-relationalMaven>=4.0.0, <4.0.6 || >=3.5.0, <3.5.12 || >=3.4.0, <=3.4.14 || >=3.0.0, <=3.3.16 || <=2.4.194.0.6, 3.5.12
Identifiers
GHSA-8r2h-xh92-gq57 · CVE-2026-41697
Weakness (CWE)
CWE-943
Tags
Published
10 Jun 2026
Updated
12 Aug 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Spring Data Relational versions 4.0.0 to before 4.0.6, 3.5.0 to before 3.5.12, and earlier affected releases do not properly escape externally supplied values used with StringMatcher (STARTING, ENDING, or CONTAINING) in Query By Example. An attacker who can supply search input can use wildcard characters to infer stored data through true/false query responses. Upgrade to Spring Data Relational 4.0.6 or 3.5.12, or a later release in the affected branch.

Written 2 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
4.8 Medium 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L CNA (vmware)
  • CISA KEV Not listed.
  • EPSS 0.0023, the 13th percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:19 UTC First seen by agentprime
  2. 31 Oct 2026, 14:19 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.