Reuse of session IDs in oatpp-mcp leads to session hijacking and prompt hijacking by remote attackers
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- Required
- Attack complexity
- High
- Impact type
- —
- Confidentiality · integrity · availability
- None · High · High
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA.
Summary
The MCP SSE endpoint in oatpp-mcp returns an instance pointer as the session ID, which is not unique nor cryptographically secure. This allows network attackers with access to the oatpp-mcp server to guess future session IDs and hijack legitimate client MCP sessions, returning malicious responses from the oatpp-mcp server.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2025-6515
- 2026-10-03 Alias added: GHSA-rvw9-mm8q-456q
References
More oatpp vulnerabilities
- TI-2025-05964 oatpp Oat++ Deserializer.cpp deserializeArray stack-based overflow CVSS 4.0MEDIUM 6.9
Sources
- CVE-2025-6515 · CVE Program
- CVE-2025-6515 · NVD
- FIRST EPSS
- GHSA-rvw9-mm8q-456q · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences