How severe is GHSA-g3jr-4jrm-jvqv?

GHSA-g3jr-4jrm-jvqv has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-g3jr-4jrm-jvqv?

GHSA-g3jr-4jrm-jvqv affects the following packages: apache-airflow-providers-elasticsearch (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-g3jr-4jrm-jvqv?

Update apache-airflow-providers-elasticsearch to 6.5.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g3jr-4jrm-jvqv is resolved across your whole dependency graph.

How do I detect GHSA-g3jr-4jrm-jvqv in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for apache-airflow-providers-elasticsearch. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-g3jr-4jrm-jvqv if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-g3jr-4jrm-jvqv?

O3 pinpoints whether GHSA-g3jr-4jrm-jvqv is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-g3jr-4jrm-jvqv actively exploited in the wild?

No public exploit code has been indexed for GHSA-g3jr-4jrm-jvqv yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-g3jr-4jrm-jvqv published, and has it been updated?

GHSA-g3jr-4jrm-jvqv was published on May 11, 2026 and was last updated on June 5, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

MEDIUM severity

GHSA-g3jr-4jrm-jvqv

MEDIUMFix: apache/airflow#65349

GHSA-g3jr-4jrm-jvqv is a medium-severity (CVSS 6.5) vulnerability in apache-airflow-providers-elasticsearch. O3 Security confirms whether GHSA-g3jr-4jrm-jvqv is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Apache Airflow Providers Elasticsearch: Elasticsearch task-log handlers leak credentials embedded in the host URL

Also known asCVE-2026-41018PYSEC-2026-22

Published

May 11, 2026

Updated

Jun 5, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jun 5, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐍apache-airflow-providers-elasticsearch

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

The Elasticsearch logging provider, when configured with a host URL that embeds credentials (for example https://user:[email protected]:9200), wrote the full host URL — including the embedded credentials — into task logs. Any user with task-log read permission could harvest the backend credentials. Users are advised to upgrade to apache-airflow-providers-elasticsearch 6.5.3 or later and, as a defense-in-depth measure, configure the backend credentials via a secret backend rather than embedding them in the [elasticsearch] host URL.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`apache-airflow-providers-elasticsearch`	all versions	6.5.3

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for apache-airflow-providers-elasticsearch. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update apache-airflow-providers-elasticsearch to 6.5.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g3jr-4jrm-jvqv is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-g3jr-4jrm-jvqv is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-g3jr-4jrm-jvqv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The Elasticsearch logging provider, when configured with a `host` URL that embeds credentials (for example `https://user:[email protected]:9200`), wrote the full host URL — including the embedded credentials — into task logs. Any user with task-log read permission could harvest the backend credentials. Users are advised to upgrade to `apache-airflow-providers-elasticsearch` 6.5.3 or later and, as a defense-in-depth measure, configure the backend credentials via a secret backend rather than embedding them in the `[elasticsearch] host` URL.

O3 Security · Impact-Aware SCA

Is GHSA-g3jr-4jrm-jvqv in your dependencies?

O3 detects GHSA-g3jr-4jrm-jvqv across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works