SUSE shibboleth-sp · Security update for shibboleth-sp
Affects SUSE shibboleth-spSource GCVE Database
Not known to be exploited · CVSS 9.1 Critical.
Data as of 31 Oct 2026, 20:20 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 31 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
SUSEsuse/shibboleth-sppkg:rpm/suse/shibboleth-spOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A security update has been released to fix this vulnerability. Users of shibboleth-sp with the replay cache configured to use an SQL database should apply the update provided by their vendor or distribution.
Description
A security update for the Shibboleth Service Provider (shibboleth-sp) addresses a high-severity SQL injection vulnerability identified as CVE-2025-9943. The flaw exists in the handling of the "ID" attribute within the SAML response when the replay cache is configured to use an SQL database for storage. This vulnerability could allow an attacker to perform SQL injection attacks against the backend database used by the replay cache.