Skip to main content
CVE-2025-22223VulnerabilityPublished Updated

Bundesamt für Sicherheit in der Informationstechnik Atlassian · VMware Tanzu Spring Security: Mehrere Schwachstellen ermöglichen Umgehen von Sicherheitsvorkehrungen

Affects Bundesamt für Sicherheit in der Informationstechnik AtlassianSource GCVE Database

0
Compare

Mentioned vulnerabilities

Not known to be exploited.

Data as of 19 Nov 2026, 02:24 UTC

Severity
High

Rated High by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Mar 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

AI-suggested

Red Hat has released security updates for affected products including Apache Camel for Spring Boot 4.8.5 and OpenShift Developer Tools 4.15. Users should apply these official updates promptly to remediate the vulnerabilities. Prior errata relevant to the system should also be applied before updating. No additional mitigation steps are indicated beyond applying these vendor-provided patches.

Description

Multiple security vulnerabilities have been identified in VMware Tanzu Spring Security and related components, including a failure to enforce maximum password length in BCryptPasswordEncoder. These issues affect Spring Security and related Red Hat products such as Apache Camel for Spring Boot and OpenShift Developer Tools. Red Hat has released security updates addressing these vulnerabilities. The vulnerabilities include potential denial of service via stack exhaustion, bypass of header filters, and improper SSL packet validation. No active exploitation in the wild has been reported.

References

Community reviews

Loading reviews…