Description

In JetBrains IntelliJ IDEA before 2026.2.1 sSRF was possible via the OpenAPI preview proxy in untrusted projects

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "6.3",
  "pubDate": "2026-08-17T16:17:52.543Z",
  "pubdate": "2026-08-17T16:17:52.543Z",
  "executiveSummary": "A Server-Side Request Forgery (SSRF) vulnerability exists in JetBrains IntelliJ IDEA before 2026.2.1.\nThe vulnerability allows malicious actors to exploit the OpenAPI preview proxy feature within the context of untrusted projects.\nSuccessful exploitation can lead to unauthorized access to internal network resources, sensitive data exposure, or interaction with internal services that are otherwise inaccessible from an external network boundary.\nThe risk implication is significant for developers or organizations handling untrusted source code repositories, as simply opening a malicious project can trigger the attack vector.\nAttacker capabilities include leveraging the development environment to act as a proxy or origin for forged requests targeting internal network infrastructure.\nExploitation requires a user to open an untrusted project containing crafted configurations that interact with the vulnerable OpenAPI preview proxy component.",
  "technicalDetails": "The vulnerability stems from insufficient input validation and improper handling of outgoing requests within the OpenAPI preview proxy functionality of JetBrains IntelliJ IDEA.\nThe vulnerable component is responsible for rendering and previewing OpenAPI specifications within the IDE environment.\nAffected versions include all releases of JetBrains IntelliJ IDEA prior to version 2026.2.1.\nThe attack flow begins when an attacker supplies an untrusted project containing maliciously crafted OpenAPI definitions or configurations designed to target arbitrary internal or external URIs via the preview proxy.\nWhen the IDE processes the OpenAPI preview proxy functionality, it fails to adequately sanitize or restrict destination URLs supplied through the preview mechanism.\nConsequently, an attacker can coerce the application into dispatching HTTP requests to arbitrary endpoints, including loopback interfaces (127.0.0.1), local network services, and internal metadata endpoints.\nNetwork exposure is localized to the machine running the affected IDE instance, but the impact extends to internal networks reachable from the host system via network routing or localhost bindings.\nAuthentication and privilege requirements are minimal from the perspective of the attacker, as the vulnerability is triggered locally through the ingestion and processing of untrusted project files.\nPayload behavior involves manipulating the request parameters within the OpenAPI preview feature to force the server-side proxy component to initiate unauthorized connections.\nPost-exploitation impact includes the potential retrieval of sensitive internal data, internal service enumeration, and potential interaction with vulnerable backend APIs running within the local network perimeter."
}