Monthly
Apache Airflow's SSH and SFTP provider hooks accept any server host key by default, so an attacker positioned as a machine-in-the-middle between an Airflow worker and an SSH or SFTP endpoint can impersonate that server and capture task credentials or transferred data. All releases of apache-airflow-providers-ssh and apache-airflow-providers-sftp before 7.0.0 are affected when a connection has neither host_key configured nor no_host_key_check explicitly disabled; the assessed vector is CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N, i.e. unauthenticated from the attacker's side but gated on the high-complexity MITM prerequisite, which is why the input's 9.1 rating overstates practical urgency. No public exploit code has been identified and EPSS is only 0.18% (7th percentile); vendor patches (provider 7.0.0) are released, and the related deferrable-SFTP path is tracked separately as CVE-2026-94135, which the same SFTP 7.0.0 release also fixes.
Erlang/OTP's ssl application in affected releases (OTP 22.2 through the fixed 27.3.4.18, 28.5.0.7 and 29.1.1) will complete a TLS 1.3 client handshake against any peer that answers with an unsolicited pre_shared_key extension, allowing that peer to impersonate the intended server while holding no certificate, no private key and no prior session. Because the bogus resumption flag short-circuits certificate handling, ssl:connect returns {ok, Socket} even though certificate path validation, verify_fun, hostname verification, partial_chain, CRL checking and OCSP stapling are all skipped; an unauthenticated network-positioned attacker (man-in-the-middle, hijacked route/DNS, or a server the client is lured into contacting) can exploit this, and clients restricted to TLS 1.2 are not affected. A vendor patch is available and no public exploit code has been identified at time of analysis.
Man-in-the-middle interception of Apache Airflow's Git provider (apache-airflow-providers-git before 0.4.1) is possible because git-over-SSH operations run with StrictHostKeyChecking=no by default, so no SSH host-key verification occurs. An attacker positioned on the network path between an Airflow worker and its Git server can impersonate the server to steal the SSH deploy key or inject malicious DAG content, leading to code execution on workers. No public exploit identified at time of analysis, and it is not listed in CISA KEV; CVSS is 8.1 (High) driven by high attack complexity (AC:H) requiring an on-path position.
Man-in-the-middle attacks against LY Corporation's Central Dogma server can compromise mirrored Git repositories in versions of the centraldogma-server-mirror-git module prior to 0.84.0, because the embedded SSH client accepts any host key presented over git+ssh:// connections. An on-path attacker between Central Dogma and the upstream Git server can impersonate that server, inject malicious commits, and silently poison every downstream consumer that reads from the mirror. No public exploit identified at time of analysis, and the issue is not listed in CISA KEV.
Man-in-the-middle exposure in Apache Airflow's `apache-airflow-providers-google` package (versions prior to 22.0.0) stems from the `ComputeEngineSSHHook` shipping with `paramiko.AutoAddPolicy` as its default missing-host-key policy, silently trusting any SSH host key presented by a Compute Engine VM. An in-path network attacker positioned between the Airflow worker and the GCE instance can intercept or tamper with the SSH session, exposing credentials, DAG-driven commands, and transferred data. No public exploit identified at time of analysis and EPSS is very low (0.02%), but technical impact is rated total by SSVC.
Attested TLS relay attacks in Cocos AI confidential computing system versions 0.4.0 through 0.8.2 enable attackers to impersonate genuine TEE-protected services on AMD SEV-SNP and Intel TDX platforms by extracting ephemeral TLS private keys and redirecting authenticated sessions. The architectural flaw allows an attacker with physical access or side-channel capabilities to relay attestation evidence to a different endpoint, breaking the authentication binding between the TEE and the client. No vendor-released patch is available; the vulnerability affects a specialized confidential computing platform with low EPSS probability (formal EPSS score not provided in input) and no public exploit identified at time of analysis, though formal ProVerif verification confirms the attack feasibility.
Authentication bypass in the Keylime registrar (versions 7.12.0 and later) lets unauthenticated network attackers perform administrative actions because the registrar fails to enforce client-side mutual TLS. Attackers connecting without a client certificate can list registered agents, read public TPM data, and delete agents - undermining the integrity of the remote-attestation trust chain. EPSS is low (0.04%, 11th percentile) and there is no public exploit identified at time of analysis, but the flaw is trivially reachable (CVSS 9.8) and patched across Red Hat and SUSE channels.
Net::LibSSH versions before 0.004 for Perl authenticate to an unverified server because connect never checks the host key against known_hosts. connect reports success as soon as ssh_connect returns SSH_OK. libssh leaves the known-hosts check to the application, and this binding never makes it, so the strict_hostkeycheck and knownhosts options are set on the session and then decide nothing. Password, agent and public-key authentication, channel and SFTP operations all run on a session whose peer was never identified, so an attacker who can redirect the connection receives the password when password authentication is used, and commands and data sent over the session.
Rex versions through 1.16.1 for Perl accept an unknown SSH host key for remote rsync transfers because sync hardcodes StrictHostKeyChecking=no. Every remote branch of sync builds its ssh command with that option, for password authentication, for private-key authentication and for the fallback. The ssh options a caller sets through set_openssh_opt reach the OpenSSH transport but not this command, so there is no configuration that restores host key checking for the transfer. An attacker who can redirect the connection before the real host key is known presents their own and the transfer proceeds: under password authentication sync sends the connection password to that server, an upload writes the selected local files to it, and a download writes what it returns to the local destination.
Apache Airflow's SFTP provider (apache-airflow-providers-sftp) omits SSH host-key verification in its deferrable code paths - SFTPTrigger, SFTPHookAsync and SFTPClientPool - because the no_host_key_check connection extra defaulted to permitting unknown hosts instead of requiring a known-hosts match. Any deployment that runs SFTP sensors or operators in deferrable mode while leaving that extra unset, supplying no host_key, and having no known_hosts entry is exposed: an unauthenticated attacker who holds a machine-in-the-middle position between the Airflow triggerer and the SFTP server can impersonate the server and capture the credentials and data exchanged (CWE-322; independent assessment scores it CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N). The vendor-released patch is apache-airflow-providers-sftp 7.0.0, which also fixes the sibling defect CVE-2026-94134 covering the synchronous SSH hook default; no public exploit code and no CISA KEV entry were identified at time of analysis, and the required MITM network position is the main factor limiting realistic risk.
Apache Airflow's SSH and SFTP provider hooks accept any server host key by default, so an attacker positioned as a machine-in-the-middle between an Airflow worker and an SSH or SFTP endpoint can impersonate that server and capture task credentials or transferred data. All releases of apache-airflow-providers-ssh and apache-airflow-providers-sftp before 7.0.0 are affected when a connection has neither host_key configured nor no_host_key_check explicitly disabled; the assessed vector is CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N, i.e. unauthenticated from the attacker's side but gated on the high-complexity MITM prerequisite, which is why the input's 9.1 rating overstates practical urgency. No public exploit code has been identified and EPSS is only 0.18% (7th percentile); vendor patches (provider 7.0.0) are released, and the related deferrable-SFTP path is tracked separately as CVE-2026-94135, which the same SFTP 7.0.0 release also fixes.
Erlang/OTP's ssl application in affected releases (OTP 22.2 through the fixed 27.3.4.18, 28.5.0.7 and 29.1.1) will complete a TLS 1.3 client handshake against any peer that answers with an unsolicited pre_shared_key extension, allowing that peer to impersonate the intended server while holding no certificate, no private key and no prior session. Because the bogus resumption flag short-circuits certificate handling, ssl:connect returns {ok, Socket} even though certificate path validation, verify_fun, hostname verification, partial_chain, CRL checking and OCSP stapling are all skipped; an unauthenticated network-positioned attacker (man-in-the-middle, hijacked route/DNS, or a server the client is lured into contacting) can exploit this, and clients restricted to TLS 1.2 are not affected. A vendor patch is available and no public exploit code has been identified at time of analysis.
Man-in-the-middle interception of Apache Airflow's Git provider (apache-airflow-providers-git before 0.4.1) is possible because git-over-SSH operations run with StrictHostKeyChecking=no by default, so no SSH host-key verification occurs. An attacker positioned on the network path between an Airflow worker and its Git server can impersonate the server to steal the SSH deploy key or inject malicious DAG content, leading to code execution on workers. No public exploit identified at time of analysis, and it is not listed in CISA KEV; CVSS is 8.1 (High) driven by high attack complexity (AC:H) requiring an on-path position.
Man-in-the-middle attacks against LY Corporation's Central Dogma server can compromise mirrored Git repositories in versions of the centraldogma-server-mirror-git module prior to 0.84.0, because the embedded SSH client accepts any host key presented over git+ssh:// connections. An on-path attacker between Central Dogma and the upstream Git server can impersonate that server, inject malicious commits, and silently poison every downstream consumer that reads from the mirror. No public exploit identified at time of analysis, and the issue is not listed in CISA KEV.
Man-in-the-middle exposure in Apache Airflow's `apache-airflow-providers-google` package (versions prior to 22.0.0) stems from the `ComputeEngineSSHHook` shipping with `paramiko.AutoAddPolicy` as its default missing-host-key policy, silently trusting any SSH host key presented by a Compute Engine VM. An in-path network attacker positioned between the Airflow worker and the GCE instance can intercept or tamper with the SSH session, exposing credentials, DAG-driven commands, and transferred data. No public exploit identified at time of analysis and EPSS is very low (0.02%), but technical impact is rated total by SSVC.
Attested TLS relay attacks in Cocos AI confidential computing system versions 0.4.0 through 0.8.2 enable attackers to impersonate genuine TEE-protected services on AMD SEV-SNP and Intel TDX platforms by extracting ephemeral TLS private keys and redirecting authenticated sessions. The architectural flaw allows an attacker with physical access or side-channel capabilities to relay attestation evidence to a different endpoint, breaking the authentication binding between the TEE and the client. No vendor-released patch is available; the vulnerability affects a specialized confidential computing platform with low EPSS probability (formal EPSS score not provided in input) and no public exploit identified at time of analysis, though formal ProVerif verification confirms the attack feasibility.
Authentication bypass in the Keylime registrar (versions 7.12.0 and later) lets unauthenticated network attackers perform administrative actions because the registrar fails to enforce client-side mutual TLS. Attackers connecting without a client certificate can list registered agents, read public TPM data, and delete agents - undermining the integrity of the remote-attestation trust chain. EPSS is low (0.04%, 11th percentile) and there is no public exploit identified at time of analysis, but the flaw is trivially reachable (CVSS 9.8) and patched across Red Hat and SUSE channels.
Net::LibSSH versions before 0.004 for Perl authenticate to an unverified server because connect never checks the host key against known_hosts. connect reports success as soon as ssh_connect returns SSH_OK. libssh leaves the known-hosts check to the application, and this binding never makes it, so the strict_hostkeycheck and knownhosts options are set on the session and then decide nothing. Password, agent and public-key authentication, channel and SFTP operations all run on a session whose peer was never identified, so an attacker who can redirect the connection receives the password when password authentication is used, and commands and data sent over the session.
Rex versions through 1.16.1 for Perl accept an unknown SSH host key for remote rsync transfers because sync hardcodes StrictHostKeyChecking=no. Every remote branch of sync builds its ssh command with that option, for password authentication, for private-key authentication and for the fallback. The ssh options a caller sets through set_openssh_opt reach the OpenSSH transport but not this command, so there is no configuration that restores host key checking for the transfer. An attacker who can redirect the connection before the real host key is known presents their own and the transfer proceeds: under password authentication sync sends the connection password to that server, an upload writes the selected local files to it, and a download writes what it returns to the local destination.
Apache Airflow's SFTP provider (apache-airflow-providers-sftp) omits SSH host-key verification in its deferrable code paths - SFTPTrigger, SFTPHookAsync and SFTPClientPool - because the no_host_key_check connection extra defaulted to permitting unknown hosts instead of requiring a known-hosts match. Any deployment that runs SFTP sensors or operators in deferrable mode while leaving that extra unset, supplying no host_key, and having no known_hosts entry is exposed: an unauthenticated attacker who holds a machine-in-the-middle position between the Airflow triggerer and the SFTP server can impersonate the server and capture the credentials and data exchanged (CWE-322; independent assessment scores it CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N). The vendor-released patch is apache-airflow-providers-sftp 7.0.0, which also fixes the sibling defect CVE-2026-94134 covering the synchronous SSH hook default; no public exploit code and no CISA KEV entry were identified at time of analysis, and the required MITM network position is the main factor limiting realistic risk.