Critical Vulnerability in libspring-java: CVE-2026-41847 Exposes Sensitive Data

libspring-java Updated 22 Oct 2026

Summary

09/06/2026
N/A
No i
Medium
4.8

DEBIAN-CVE-2026-41847: ... Affects libspring-java versions 4.3.30-1 – 4.3.30-4. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

libspring-java is a widely used library in Java applications that provides comprehensive support for building enterprise-level applications. It offers features such as dependency injection, aspect-oriented programming, and transaction management. However, the library is currently vulnerable to CVE-2026-41847, which could potentially lead to data exposure.

Vulnerability Detail

CVE-2026-41847 is a vulnerability that arises from improper handling of user input in libspring-java. This flaw allows attackers to exploit the library to access sensitive data, which could lead to unauthorized information disclosure. The vulnerability affects multiple Debian distributions, including Bullseye, Bookworm, Trixie, and Forky, and has a CVSS score of 4.8, indicating a moderate severity level. If left unaddressed, this vulnerability can have significant ramifications for applications relying on this library, potentially compromising user data and application integrity.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, you can restrict access to the affected components of the application or implement input validation to mitigate the risk of exploitation until a patch is applied.

Conclusion

CVE-2026-41847 represents a significant vulnerability in the libspring-java library, which could expose sensitive data if not addressed. It is crucial for developers and system administrators to update their libraries and implement necessary workarounds to safeguard their applications.

See every vulnerability recorded for libspring-java →

Share this vulnerability

FAQ

CVE-2026-41847 is a vulnerability in the libspring-java library that allows unauthorized access to sensitive data due to improper input handling.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

If exploited, this vulnerability can lead to unauthorized data access, compromising user information and application security.

Yes, a patched version of libspring-java is available. You should update to the latest version using your package manager.

The CVSS score of CVE-2026-41847 is 4.8, indicating a moderate level of severity.

Related vulnerabilities

Recent vulnerabilities recorded for libspring-java.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback