dbcve.org
AirflowApplication · Apache

CVE-2025-62402

MEDIUM · 5.4 CVSS v3.1 Published 2025-10-30
Fix available
A fix is available. Upgrade to 3.1.1 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
API users via `/api/v2/dagReports` could perform Dag code execution in the context of the api-server if the api-server was deployed in the environment where Dag files were available.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Authenticated API users accessing /api/v2/dagReports can execute arbitrary code through DAG files if those files are accessible in the api-server's deployment environment, executing in the context of the api-server with its privileges.

MitigationRestrict API access to /api/v2/dagReports to authorized users only, ensure DAG files are not accessible from the api-server's environment, and implement proper sandboxing for DAG code execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AirflowApplication
Affected:>= 3.0.0, < 3.1.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Airflow version
    Run 'airflow version' or 'pip show apache-airflow' to identify the installed version
    Affected if Version is 3.0.0 through 3.0.x or 3.1.0 (i.e., >= 3.0.0 and < 3.1.1)
  2. Verify API server is enabled
    Check if the Airflow API server component is running via process list (ps aux | grep airflow) or Kubernetes/Docker deployment status
    Affected if The api-server process is running and the REST API is accessible on port 8080 or configured API port
  3. Confirm /api/v2/dagReports endpoint is exposed
    Review Airflow config file (airflow.cfg) under [api] section, or check API server routing configuration for '/api/v2/dagReports' exposure
    Affected if The endpoint is accessible without additional restrictions beyond basic authentication
  4. Identify DAG files accessible to api-server
    Check the dags_folder path in airflow.cfg (typically $AIRFLOW_HOME/dags) and verify if DAG files exist in directories readable by the api-server process
    Affected if DAG files are present in a folder that the api-server process can read from its deployment environment
  5. Review API authentication settings
    Inspect airflow.cfg [api] section for auth backend settings, and check if RBAC is properly configured to restrict /api/v2/dagReports access to authorized users only
    Affected if The API accepts authenticated requests without granular authorization controls on the dagReports endpoint

You are affected if running Airflow 3.0.0-3.1.0 with the API server enabled and DAG files accessible to the api-server process, allowing authenticated users to trigger arbitrary code execution via the /api/v2/dagReports endpoint.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.1.1 or later
Fixed in 3.1.1
Interim mitigation

Restrict API access to /api/v2/dagReports to authorized users only, ensure DAG files are not accessible from the api-server's environment, and implement proper sandboxing for DAG code execution.

Recommended fix High confidence

3.1.1

  1. Verify current Airflow version with `airflow version` or check your requirements.txt/pip freeze
  2. Stop all Airflow services (scheduler, webserver, triggerer, etc.)
  3. Upgrade Airflow using pip: `pip install 'apache-airflow>=3.1.1'`
  4. Verify the upgrade was successful: `airflow version` (should show 3.1.1 or later)
  5. Restart all Airflow services
  6. Test the `/api/v2/dagReports` endpoint to confirm it no longer allows arbitrary DAG code execution
Caveat Review Apache Airflow 3.1.1 release notes for any breaking changes between 3.0.x and 3.1.x

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Airflow Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-62402 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-62402 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data