ZDF
Sign inSign up

Vulnerabilities

Vulnerability · GHSA-4jw7-6mqj-vrhq

Server-side request forgery in AI chat file downloads bypasses the outbound IP deny-list

Published Aug 20, 2026 · catalog updated Aug 20, 2026 · Server-side request forgery in

Last checked Nov 1, 2026. A connected source was read within the last 7 days.

Open the advisory

Exploitation likelihood is not on this record for GHSA-4jw7-6mqj-vrhq. A missing EPSS score is not a low risk. Compare Server-side request forgery in with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Server-side request forgery in).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
High7.7
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Version ranges on file
Affected products
npm directus

## Summary The AI chat endpoint ( ) fetches user-supplied URLs server-side without the IP validation Directus applies to its other outbound requests. A chat message may include a file part, and the URL carried by that part is passed to the AI SDK, which downloads any file the target model cannot handle natively using a plain . That download does not go through Directus's IP-validated HTTP agent, so the control does not apply to it. The AI SDK has its own download guard, but it only rejects literal private IP addresses and the family and performs no DNS resolution. A public hostname that resolves to a private address (for example a name pointing at or ) therefore passes the check and is fetched. Any authenticated user with app access can use this to make the Directus server issue requests to internal-only destinations. Administrator rights are not required. ## Details Directus passes client-supplied chat messages to the AI SDK's after converting them to model messages. For any file or image part whose URL the configured model does not support natively, the SDK downloads the content itself using the default download function, which calls global directly. Every other server-side fetch in Directus goes through ( ), which resolves the target host and rejects denied addresses; the AI SDK download path did not, so the deny-list was not enforced there. The URL used for that download is attacker-controlled: - From 11.16.0 onward, rewrites each file part's with the value of taken from the request body. That value is expected to be an opaque provider file id and was not validated as such, so a URL placed there becomes the download target. - In 11.14.0 through 11.15.x, before that rewrite existed, the file part's field itself was passed through unvalidated and served as the download target. The SDK's guard blocks literal private IP addresses and the , , and hostnames. Because it does not resolve DNS, a public hostname whose A record points into private space is accepted, and th

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • npm directus>= 11.16.0, < 12.2.0

How to fix GHSA-4jw7-6mqj-vrhq

  • Upgrade

    GHSA-4jw7-6mqj-vrhq lists a fix boundary at 12.2.0. Compare the installed build with that boundary before you change production.

  • Version check

    Affected < 12.2.0

  • Advisory

    Open the inventory_github record and follow its fix.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for GHSA-4jw7-6mqj-vrhq. A missing EPSS score is not a low risk. Compare Server-side request forgery in with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with >= 11.16.0, < 12.2.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-918: Server-Side Request Forgery (SSRF). EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Directus security

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Aug 20, 2026 · Maintainer security tabs

    Detected

    ## Summary The AI chat endpoint ( ) fetches user-supplied URLs server-side without the IP validation Directus applies to its other outbound requests. A chat message may include a file part, and the URL carried by that part is passed to the AI SDK, which downloads any file the target model cannot handle natively using a plain . That download does not go through Directus's IP-validated HTTP agent, s

Sources

  • Maintainer security tabsVendor advisoryGHSA-4jw7-6mqj-vrhq

    ## Summary The AI chat endpoint ( ) fetches user-supplied URLs server-side without the IP validation Directus applies to its other outbound requests. A chat message may include a file part, and the URL carried by that part is passed to the AI SDK, which downloads any file the target model cannot handle natively using a plain . That download does not go through Directus's IP-validated HTTP agent, s

    github.com

Freshness

Last verified in this catalog Aug 20, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • Maintainer security tabsNov 1, 2026