VulnerabilityPublished 11 May 2026

CVE-2026-41018: Apache Airflow Providers Elasticsearch · Sensitive Data in Logs

Affects Apache Airflow Providers ElasticsearchSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 6.5.3 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

6.5Medium

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 35% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 6.5.3

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

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

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
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: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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

Upgrade Apache Airflow Providers Elasticsearch and apache-airflow-providers-elasticsearch to 6.5.3.

Affected software

Product	Affected	Fixed in
Apache Software FoundationApache Airflow Providers Elasticsearch	Affected <6.5.3	Fixed in 6.5.3
PyPIapache-airflow-providers-elasticsearch`pkg:pypi/apache-airflow-providers-elasticsearch`Other threats	Affected <6.5.3	Fixed in 6.5.3

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

AI-suggested

Users should upgrade to apache-airflow-providers-elasticsearch version 6.5.3 or later where this issue is fixed. Additionally, as a defense-in-depth measure, credentials should not be embedded directly in the Elasticsearch host URL but configured via a secret backend. Patch status is not explicitly confirmed in the advisory, but the upgrade recommendation indicates a fix is available in 6.5.3+.

Description

CVE-2026-41018 is a vulnerability in the Apache Airflow Providers Elasticsearch logging integration where credentials embedded in the Elasticsearch host URL are written in full to task logs. This exposure allows any user with permission to read task logs to access sensitive backend credentials. The vulnerability has a medium severity with a CVSS score of 6.5. Users are advised to upgrade to version 6.5.3 or later and to avoid embedding credentials directly in the host URL by using a secret backend configuration instead.

Impact

Any user with permission to read task logs can obtain backend Elasticsearch credentials embedded in the host URL, potentially leading to unauthorized access to Elasticsearch resources. The confidentiality of sensitive credentials is compromised, but integrity and availability are not directly affected.

Summary

The Apache Airflow Providers Elasticsearch logging provider, when configured with a host URL containing embedded credentials (e.g., https://user:password@server.example.com:9200), logs the entire URL including credentials into task logs. This results in sensitive information leakage (CWE-532: Insertion of Sensitive Information into Log File). The vulnerability affects all versions prior to 6.5.3. The CVSS 3.1 base score is 6.5, reflecting network attack vector, low attack complexity, requiring privileges to read logs, no user interaction, unchanged scope, and high confidentiality impact.

CWE-532Insertion of Sensitive Information into Log File (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A09:2025: Security Logging & Alerting Failures (opens in a new tab)
The product writes sensitive information to a log file.
Architecture and Design · Implementation
Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
Distribution
Remove debug log files before deploying the application into production.
Operation
Protect log files against unauthorized read/write.
OWASP Cheat Sheets
Application Logging Vocabulary (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V7.1.1 (opens in a new tab)
V7.1.2 (opens in a new tab)
V8.3.5 (opens in a new tab)
Attack patterns
Fuzzing for application mapping (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 18 May 2026, 10:48 UTC

WeaknessesCWE-532

Technical details

References

Community reviews

Related threats