CVE-2025-51481VulnerabilityPublished 22 Jul 2025Updated 26 Oct 2026

Dagster ge: Local File Inclusion

Affects dagster-geSource GCVE Database

Authoritative record:CVE-2025-51481· Medium 6.6

Not known to be exploited · CVSS 6.6 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

6.6Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:L

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
PyPIdagster-ge`pkg:pypi/dagster-ge`Other threats	Affected 0.10.0 – 0.14.16rc2 <=1.10.14 200 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, restrict access to the gRPC server to trusted users only and monitor for suspicious activity related to ExternalNotebookData requests.

Description

A Local File Inclusion (LFI) vulnerability exists in Dagster version 1.10.14 and earlier versions, including several 0.10.x releases. The flaw is in the dagster._grpc.impl.get_notebook_data function, where attackers with access to the gRPC server can read arbitrary files by exploiting path traversal in the notebook_path field of ExternalNotebookData requests. This bypasses the intended extension-based file access checks.

Impact

Successful exploitation allows an attacker with access to the gRPC server to read arbitrary files on the host system, potentially exposing sensitive information. The confidentiality impact is high, while integrity and availability impacts are low. The attack requires local access to the gRPC server and user interaction, limiting the attack surface.

Summary

The vulnerability in Dagster ge (CVE-2025-51481) allows an attacker with access to the gRPC server interface to perform Local File Inclusion via the notebook_path parameter in ExternalNotebookData requests. By supplying path traversal sequences, the attacker can bypass extension-based restrictions and read arbitrary files on the server. This affects Dagster versions up to and including 1.10.14 and multiple 0.10.x versions. The CVSS 3.1 score is 6.6 (medium severity), reflecting local attack vector with low privileges required but user interaction needed, and high confidentiality impact with limited integrity and availability impact.

References

Community reviews

Loading reviews…