ZDF
Sign inSign up

Vulnerabilities

Vulnerability · GHSA-6hpw-rhhq-6xq3

Unauthenticated telemetry submission and settings write via pre-authorization side effects on the project owner endpoint

Published Aug 5, 2026 · catalog updated Aug 5, 2026 · Unauthenticated telemetry submission and

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-6hpw-rhhq-6xq3. A missing EPSS score is not a low risk. Compare Unauthenticated telemetry submission and 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 (Unauthenticated telemetry submission and).
  • 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
Medium5.3
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Version ranges on file
Affected products
npm directus

## Summary The endpoint derives its authorization from the settings singleton write it performs, which passes through the permission layer. In affected versions two side effects ran before that write: an outbound owner report to the configured compliance intake endpoint containing request-supplied fields, and, if that report failed, a direct database write setting to . Directus populates accountability globally but does not reject unauthenticated requests at the middleware layer, so an unauthenticated caller received while both side effects had already been dispatched. ## Details The route has no per-route authorization guard. The outbound report was issued ahead of the settings write and was intentionally not awaited, so it continued to settle after the outer request had already failed with a permission error. The report is a POST to the configured compliance endpoint ( , default ) whose body is assembled from the request payload ( , , , ) together with the instance's and version. Every payload field is caller-supplied and none are validated before the report is sent. The destination is fixed by configuration and is not influenced by the request. The rejection handler attached to that call performed a direct query-builder update of , bypassing the permission layer entirely. This path is reached only when the outbound report fails, which is the standing condition on deployments with restricted outbound network access. is the flag read by the daily project status job, which re-sends the stored owner information and then clears the flag. An unauthenticated read of from the settings table also preceded the check. That value is not returned to the caller and is not disclosed. Both side effects require , which is enabled by default. With it disabled the reporting helper returns before issuing any request, and neither side effect occurs. ## Impact An unauthenticated caller able to reach the API could: - Cause the instance to submit caller-controlled strings to the configu

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.13.0, < 12.1.0

How to fix GHSA-6hpw-rhhq-6xq3

  • Upgrade

    GHSA-6hpw-rhhq-6xq3 lists a fix boundary at 12.1.0. Compare the installed build with that boundary before you change production.

  • Version check

    Affected < 12.1.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-6hpw-rhhq-6xq3. A missing EPSS score is not a low risk. Compare Unauthenticated telemetry submission and with the linked advisory before you change production.

Which versions are affected?

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

What should an analyst verify?

CWE-696; CWE-862: Missing Authorization. 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 5, 2026 · Maintainer security tabs

    Detected

    ## Summary The endpoint derives its authorization from the settings singleton write it performs, which passes through the permission layer. In affected versions two side effects ran before that write: an outbound owner report to the configured compliance intake endpoint containing request-supplied fields, and, if that report failed, a direct database write setting to . Directus populates accountab

Sources

  • Maintainer security tabsVendor advisoryGHSA-6hpw-rhhq-6xq3

    ## Summary The endpoint derives its authorization from the settings singleton write it performs, which passes through the permission layer. In affected versions two side effects ran before that write: an outbound owner report to the configured compliance intake endpoint containing request-supplied fields, and, if that report failed, a direct database write setting to . Directus populates accountab

    github.com

Freshness

Last verified in this catalog Aug 5, 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