cve.bz

CVE-2026-41018 apache apache-airflow-providers-elasticsearch

6.5 mediumEPSS 0.4%Fix available

Medium (6.5) in apache apache-airflow-providers-elasticsearch. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in apache-airflow-providers-elasticsearch 6.5.3.

On this page
The Elasticsearch logging provider, when configured with a `host` URL that embeds credentials (for example `https://user:password@server.example.com: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.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 36th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-05-11. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-532 Insertion of Sensitive Information into Log File
OWASP Top 10
A09:2025 Logging & Alerting Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-41018 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-41018?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-41018?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-41018 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-41018

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-41018](https://cve.bz/cve/badge/CVE-2026-41018.svg)](https://cve.bz/cve/CVE-2026-41018)

HTML:

<a href="https://cve.bz/cve/CVE-2026-41018"><img src="https://cve.bz/cve/badge/CVE-2026-41018.svg" alt="CVE-2026-41018"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Airflow Providers Elasticsearchbefore 6.5.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-g3jr-4jrm-jvqvPyPIapache-airflow-providers-elasticsearch<6.5.36.5.3
PYSEC-2026-22PyPIapache-airflow-providers-elasticsearch<6.5.36.5.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu16.04:LTSelasticsearchno fix listedUBUNTU-CVE-2026-41018

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu.

Attack patterns (CAPEC)

  • CAPEC-215 Fuzzing for application mapping Likelihood: High · Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON