CVE-2026-41719
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA SpEL Injection vulnerability exists in the Spring Data KeyValue if unsanitized user input is passed as Sort into a repository query method that delegates evaluation to the SpelPropertyComparator. Affected versions: Spring Data KeyValue / Spring Data Redis 4.0.0 through 4.0.5; 3.5.0 through 3.5.11; 3.4.0 through 3.4.14; 3.3.0 through 3.3.16; 3.2.0 through 3.2.15; 3.1.0 through 3.1.14; 3.0.0 through 3.0.15; 2.7.0 through 2.7.19.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA SpEL Injection vulnerability in Spring Data KeyValue (also affecting Spring Data Redis) allows attackers to execute arbitrary Spring Expression Language statements by providing unsanitized user input as the Sort parameter to repository query methods that delegate to SpelPropertyComparator for evaluation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 2.7.0, < 2.7.20>= 3.0.0, < 3.0.16>= 3.1.0, < 3.1.15>= 3.2.0, < 3.2.16>= 3.3.0, < 3.3.17>= 3.4.0, < 3.4.15>= 3.5.0, < 3.5.11.1>= 4.0.0, < 4.0.5.1>= 2.7.0, < 2.7.20>= 3.0.0, < 3.0.16>= 3.1.0, < 3.1.15>= 3.2.0, < 3.2.16>= 3.3.0, < 3.3.17>= 3.4.0, < 3.4.15>= 3.5.0, < 3.5.11.1>= 4.0.0, < 4.0.5.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Spring Data KeyValue or Redis dependency versionInspect your project's build file (pom.xml, build.gradle, or equivalent) to find the exact version of org.springframework.data:spring-data-keyvalue or org.springframework.data:spring-data-redisAffected if The version falls within any of these ranges: >= 2.7.0 and < 2.7.20; >= 3.0.0 and < 3.0.16; >= 3.1.0 and < 3.1.15; >= 3.2.0 and < 3.2.16; >= 3.3.0 and < 3.3.17; >= 3.4.0 and < 3.4.15; >= 3.5.0 and < 3.5.11.1; >= 4.0.0 and < 4.0.5.1
-
Locate repository interfaces using Sort parametersSearch your codebase for repository method signatures that accept org.springframework.data.domain.Sort (or Sort as type) parameters, such as 'List<Entity> findAll(Sort sort)' or custom query methods that accept SortAffected if Your application defines repository methods accepting Sort parameters that could be invoked with user-supplied input
-
Trace user input to Sort parameter usageReview controller or service code that passes request parameters (query parameters, path variables, or request body fields) directly to repository Sort arguments without validationAffected if User-controlled data flows directly into Sort parameters without sanitization or allowlist validation
-
Verify SpelPropertyComparator is in useCheck if the application uses Spring Data Redis or KeyValue repositories that rely on SpelPropertyComparator for sorting, typically evident in sorting operations against Redis or KeyValue storesAffected if Repository sorting operations delegate to SpelPropertyComparator, which evaluates SpEL expressions from Sort input
Your environment is affected if you use a vulnerable version of Spring Data KeyValue or Redis AND pass unsanitized user input to Sort parameters in repository query methods.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.7.203.0.163.1.15
Sanitize and validate all user-supplied input before using it as Sort parameters in repository query methods, or upgrade to a patched version when available. Implement allowlist-based input validation for Sort field names.
Spring Data KeyValue/Redis 2.7.20, 3.0.16, 3.1.15, 3.2.16, 3.3.17, 3.4.15, 3.5.12, or 4.0.6 (or later)
- 1. Identify the exact version of Spring Data KeyValue or Spring Data Redis in use by checking build configuration files (e.g., pom.xml, build.gradle).
- 2. Determine the project version line being used (2.7.x, 3.0.x, 3.1.x, 3.2.x, 3.3.x, 3.4.x, 3.5.x, or 4.0.x).
- 3. Upgrade to the first fixed version in that line: for 2.7.x upgrade to 2.7.20; for 3.0.x upgrade to 3.0.16; for 3.1.x upgrade to 3.1.15; for 3.2.x upgrade to 3.2.16; for 3.3.x upgrade to 3.3.17; for 3.4.x upgrade to 3.4.15; for 3.5.x upgrade to 3.5.12; for 4.0.x upgrade to 4.0.6.
- 4. Alternatively, upgrade to the latest available version which includes the fix (e.g., 2.7.x line latest, 3.0.x line latest, etc.).
- 5. Update the dependency version in pom.xml or build.gradle.
- 6. Rebuild the project and run tests to verify the upgrade does not break existing functionality.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41719 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-41719 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data