An attack pattern where a vulnerable server is tricked into making requests on the attacker’s behalf. In application exploitation, SSRF can be used to reach internal resources, fetch malicious payloads, or amplify a flaw into full code execution.
Expanded Definition
Server-Side Request Forgery, or SSRF, is an exploitation pattern where an attacker induces a server, application, or AI-enabled backend to send requests it should not send. The risk is especially serious in NHI environments because the outbound request often inherits internal trust, network reach, or service credentials. In practice, SSRF can be used to probe private IP space, access metadata services, retrieve tokens, or pivot into systems that are not internet-facing. Guidance across vendors is consistent on the core behavior, but the blast radius depends on how the server is connected, what egress controls exist, and whether secrets are exposed to the request path. For broader governance context, NHI Management Group treats this as a trust-boundary failure rather than a simple input-validation issue, which aligns with the intent of the NIST Cybersecurity Framework 2.0. The most common misapplication is treating SSRF as only a web application bug, which occurs when defenders ignore how outbound server requests can reach internal identity and secret-bearing endpoints.
Examples and Use Cases
Implementing SSRF defenses rigorously often introduces URL-validation, egress-filtering, and network-segmentation overhead, requiring organisations to weigh application flexibility against attack-path reduction.
- A file import feature fetches remote URLs and is abused to request internal metadata endpoints that return temporary credentials.
- An AI agent with tool access is prompted to retrieve a URL, and the backend performs the fetch with privileged network access instead of user-level access.
- A webhook tester accepts arbitrary destinations and is turned into a proxy for scanning RFC1918 addresses and internal admin services.
- A document preview service follows redirects and is used to reach hidden infrastructure or internal APIs that were never meant to be callable externally.
- An exposed integration service leaks secrets because the server-side fetch path can read URLs embedded in configuration, similar to patterns discussed in the JetBrains GitHub plugin token exposure research context.
These cases illustrate why SSRF is not just about blocking one endpoint. It is about controlling where server-initiated traffic can go, what it can learn, and which identities or credentials it can reach along the way. For implementation guidance, the OWASP testing model for request handling is often paired with the identity and access principles in NIST materials, including the NIST Cybersecurity Framework 2.0.
Why It Matters in NHI Security
SSRF becomes an NHI problem the moment a server can reach secret stores, identity endpoints, or internal APIs using credentials that were never intended to face hostile input. That is why NHI Management Group emphasizes least privilege, strict secret containment, and visible service-account governance. The risk is amplified by how commonly secrets are stored outside protected systems: NHI Mgmt Group reports that 96% of organisations store secrets outside of secrets managers in vulnerable locations including code, config files, and CI/CD tools. When SSRF can query those locations or the systems behind them, a single bug can become a credential-exposure event, a lateral-movement path, or a supply-chain incident. This also connects to secret hygiene patterns highlighted in the Ultimate Guide to NHIs, where weak visibility and rotation discipline increase the duration of compromise. Organisations typically encounter the operational impact only after internal endpoints are probed or tokens are stolen, at which point SSRF becomes unavoidable to address.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP Non-Human Identity Top 10 and OWASP Agentic AI Top 10 address the attack and risk surface, while NIST CSF 2.0 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP Non-Human Identity Top 10 | NHI-02 | SSRF often exposes secrets and service-account paths covered by NHI secret-management controls. |
| NIST CSF 2.0 | PR.AC-4 | SSRF is a trust-boundary failure that weakens access control and internal network isolation. |
| OWASP Agentic AI Top 10 | Agentic tools that fetch URLs can be coerced into SSRF through indirect prompt and tool abuse. |
Apply least privilege, segment internal services, and limit which destinations servers can reach.
Related resources from NHI Mgmt Group
Deepen Your Knowledge
Reviewed and updated by the NHIMG editorial team on June 7, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org
