CVE-2025-59163
Raw vector
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:A/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2025-59163 is a low-severity Reliance on Reverse DNS Resolution for a Security-Critical Action (CWE-350) vulnerability. Its CVSS base score is 2.1 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 31th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
This vulnerability is AI-related — categorised as AI Agent Protocols and Integrations; in the Protocol-Specific Risks risk domain.
The strongest mitigations our analysis identified map to IA-3 (Device Identification and Authentication) and SC-20 (Secure Name/Address Resolution Service (Authoritative Source)) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-31583
Vulnerability Data
vet is an open source software supply chain security tool. Versions 1.12.4 and below are vulnerable to a DNS rebinding attack due to lack of HTTP Host and Origin header validation. Data from the vet scan sqlite3 database may be…
more
exposed to remote attackers when vet is used as an MCP server in SSE mode with default ports through the sqlite3 query MCP tool. This issue is fixed in version 1.12.5.
- CWE(s)
AI Security AnalysisAI
- AI Category
- AI Agent Protocols and Integrations
- Risk Domain
- Protocol-Specific Risks
- OWASP Top 10 for LLMs 2025
- None mapped
- Classification Reason
- Matched keywords: mcp
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Requiring unique device identification and authentication before any connection prevents security decisions based solely on unverified reverse DNS lookups.
Mandating data-origin authentication for name/address resolution stops reliance on unauthenticated reverse DNS responses.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Strong authentication of users/services/hardware directly prevents security decisions based on unauthenticated reverse DNS.
Monitoring DNS services can detect adverse events stemming from unverified reverse lookups.
Network protections reduce the feasibility of attackers exploiting unauthenticated reverse-DNS decisions.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Network security controls can enforce authenticated, non-DNS-based host identification.
Secure network services discourage use of unauthenticated reverse-DNS for access decisions.
Application security requirements can mandate authenticated host verification instead of reverse DNS.
Secure architecture principles discourage reliance on unauthenticated DNS for security decisions.
Secure coding practices can replace reverse-DNS checks with cryptographically verified identities.
Strong authentication mechanisms reduce reliance on unauthenticated DNS-based identity decisions.