CVE-2025-27089

MEDIUMNVD 5.45.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 5.4 from GitHub Security Advisory (severity: MODERATE) published 2025-02-19. NVD baseline CVSS 5.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekElevated

Also known asEUVD-2025-4664 (ENISA EUVD) · GHSA-99vm-5v2h-h6r6 (GitHub Security Advisories)Source: ENISA EUVD

5.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.4Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Directus is a real-time API and App dashboard for managing SQL database content. In affected versions if there are two overlapping policies for the update action that allow access to different fields, instead of correctly checking access permissions against the item they apply for the user is allowed to update the superset of fields allowed by any of the policies. E.g. have one policy allowing update access to field_a if the id == 1 and one policy allowing update access to field_b if the id == 2. The user with both these policies is allowed to update both field_a and field_b for the items with ids 1 and 2. Before v11, if a user was allowed to update an item they were allowed to update the fields that the single permission, that applied to that item, listed. With overlapping permissions this isn't as clear cut anymore and the union of fields might not be the fields the user is allowed to update for that specific item. The solution that this PR introduces is to evaluate the permissions for each field that the user tries to update in the validateItemAccess DB query, instead of only verifying access to the item as a whole. This is done by, instead of returning the actual field value, returning a flag that indicates if the user has access to that field. This uses the same case/when mechanism that is used for stripping out non permitted field that is at the core of the permissions engine. As a result, for every item that the access is validated for, the expected result is an item that has either 1 or null for all the "requested" fields instead of any of the actual field values. These results are not useful for anything other than verifying the field level access permissions. The final check in validateItemAccess can either fail if the number of items does not match the number of items the access is checked for (ie. the user does not have access to the item at all) or if not all of the passed in fields have access permissions for any of the returned items. This is a vulnerability that allows update access to unintended fields, potentially impacting the password field for user accounts. This has been addressed in version 11.1.2 and all users are advised to upgrade. There are no known workarounds for this vulnerability.

CVSS v3
5.4
EG Score
5.4MEDIUMmedium confidence
EG Risk
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity54% × 45%
Impact severity (EG Severity): CVSS 5.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
14th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.4): severity, escalated by confirmed exploitation. This CVE's 5.4 is its impact severity (EG Severity), not escalated.

EG Severity
5.4 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

February 19, 2025

Last Modified

February 27, 2025

References (2)

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmdirectus @ 11.1.2 (fixes >= 11.0.0, < 11.1.2)—ghsa
npm@directus/api @ 23.1.0 (fixes >= 22.0.0, < 23.1.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 1 ecosystem)
npm(2)
PackageVulnerable rangeFix by version rangeDependents
directus—
  • 11.0.0 up to 11.1.2: fixed in 11.1.2
—
@directus/api—
  • 22.0.0 up to 23.1.0: fixed in 23.1.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 39× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 96 of 195 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 99 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:42 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  2. 2026-11-01 16:32 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  3. 2026-11-01 08:08 UTCGHSA enrichmentGHSA-99vm-5v2h-h6r6 · GitHub severity MODERATE · GitHub CVSS 5.4
  4. 2026-11-01 08:08 UTCEG score recompute
  5. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  6. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  7. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  8. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  9. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  10. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  11. 2026-10-25 16:38 UTCEG score recompute
  12. 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  13. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  14. 2026-10-24 00:38 UTCEG score recompute
  15. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  16. 2026-10-22 16:32 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  17. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  18. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  19. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  20. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  21. 2026-10-18 05:42 UTCEG score recompute
  22. 2026-10-17 16:32 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  23. 2026-10-16 16:38 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  24. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  25. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.2% · 13th percentile
Show 71 more
  1. 2026-10-13 16:32 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  2. 2026-10-12 17:14 UTCEG score recompute
  3. 2026-10-12 16:32 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  4. 2026-10-11 20:46 UTCEG score recompute
  5. 2026-10-11 18:57 UTCEG score recompute
  6. 2026-10-11 15:35 UTCEG score recompute
  7. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  8. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  9. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  10. 2026-10-08 17:09 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  11. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  12. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  13. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  14. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  15. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  16. 2026-10-02 22:40 UTCOSV refresh
  17. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  18. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  19. 2026-09-29 15:19 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  20. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  21. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  22. 2026-09-26 00:24 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  23. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  24. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  25. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  26. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.2% · 15th percentile
  27. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  28. 2026-09-16 05:13 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  29. 2026-09-13 20:09 UTCOSV refresh
  30. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  31. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  32. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  33. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  34. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  35. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  36. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  37. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  38. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  39. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  40. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  41. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  42. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  43. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  44. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  45. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  46. 2026-08-25 21:39 UTCOSV refresh
  47. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  48. 2026-08-24 14:16 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  49. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  50. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  51. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  52. 2026-08-18 13:47 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  53. 2026-08-17 13:46 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  54. 2026-08-16 14:55 UTCEPSS rescoreEPSS 0.2% · 14th percentile
  55. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  56. 2026-08-15 01:29 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  57. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  58. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  59. 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  60. 2026-08-09 14:10 UTCOSV refresh
  61. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  62. 2026-08-07 16:26 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  63. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  64. 2026-08-05 19:16 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  65. 2026-08-04 15:09 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  66. 2026-08-04 10:37 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  67. 2026-08-03 10:35 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  68. 2026-08-02 02:26 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  69. 2026-08-01 04:15 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  70. 2026-07-30 16:27 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  71. 2026-07-30 01:29 UTCEPSS rescoreEPSS 0.2% · 13th percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2025-27089?
CVE-2025-27089 is a medium-severity vulnerability; its CVE record was published on February 19, 2025. Directus is a real-time API and App dashboard for managing SQL database content. In affected versions if there are two overlapping policies for the update action that allow access to different fields, instead of correctly checking access permissions against the item they apply for the user is…
When was the CVE record for CVE-2025-27089 published?
The CVE record for CVE-2025-27089 was published on February 19, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of February 27, 2025; the record at its source may have been updated since.
Is CVE-2025-27089 actively exploited?
CVE-2025-27089 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (14th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-27089?
CVE-2025-27089 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2025-27089?
A fix for CVE-2025-27089 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-27089

Explore →

Is Your Infrastructure Affected by CVE-2025-27089?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs