Monthly
openssl_encrypt by jahlives (versions before 1.4.9) embeds an unkeyed SHA-256 digest of each plaintext document into the encrypted file's cleartext header, creating a passive plaintext-confirmation oracle. Any party who possesses an encrypted file - including unauthorized recipients of intercepted or leaked archives - can extract this hash without the encryption password and use it to verify guessed or known plaintexts via offline dictionary attacks. Additionally, because the hash is unkeyed and deterministic, identical source documents encrypted separately under different passwords produce matching header hashes, enabling cross-file correlation and fingerprinting that undermines the confidentiality guarantees users expect from file encryption. No public exploit code has been identified at time of analysis, and this vulnerability does not appear in CISA KEV.
Sensitive-file exposure in the openssl-encrypt pip package (openssl_encrypt) at versions <= 1.4.8 stems from its 'Encrypted USB Workspace' feature writing a marker that falsely declares the workspace AES-256-GCM encrypted while the derived key is never applied and the directory remains in cleartext. Users who trust the branding and store files in the workspace leave them fully readable on the removable media, so anyone with physical possession of the USB device can recover the data. No public exploit identified at time of analysis and the flaw is not in CISA KEV, but the failure silently defeats the product's core security promise.
Cleartext exposure of Wi-Fi credentials in DJI consumer and prosumer drones lets an attacker within Bluetooth range recover the drone's Wi-Fi SSID, PSK, and trusted-client UUID by passively sniffing unencrypted DUML-over-BLE messages exchanged during a normal DJI Fly connection or QuickTransfer handoff. This affects a broad range of current DJI models (Neo, Flip, Air 3/3S, Avata 2/360, Mavic 3 family, Mavic 4 Pro, and Mini 2 through Mini 5 Pro) below specific firmware versions. Recovered credentials grant the attacker access to the drone's internal Wi-Fi network and the ability to decrypt the operator's Wi-Fi traffic; no public exploit identified at time of analysis, and it is not listed in CISA KEV.
Unencrypted data transmission in Samsung Smart Switch prior to version 3.7.72.6 exposes sensitive personal data to interception by adjacent network attackers. An attacker positioned on the same network segment can passively capture data flowing between devices during an active Smart Switch wireless transfer session. No public exploit has been identified and no CISA KEV listing exists, but the adjacent-network vector and low attack complexity make this a realistic threat on shared or untrusted Wi-Fi networks.
Missing-encryption weaknesses in Cisco RoomOS software (the OS for Cisco Webex/Room collaboration endpoints) were fixed in an internal-hardening release covering multiple internally discovered issues grouped under CWE-311. Because sensitive data or communications are not adequately encrypted, network-positioned attackers could intercept or expose information handled by affected devices. There is no public exploit identified at time of analysis and this CVE is not in CISA KEV; EPSS is negligible at 0.06% (0th percentile), consistent with SSVC 'Exploitation: none.' Note the published CVSS 9.8 (C:H/I:H/A:H) sits uneasily against a CWE-311/Information-Disclosure classification, which normally implies a confidentiality-centric impact.
Authenticated principal impersonation in CoreWCF (versions >=1.9.0, <1.9.1) occurs because the SPNEGO SecurityContextToken proof key returned in the RequestSecurityTokenResponse (RSTR) is wrapped without confidentiality protection, allowing any on-path observer to recover it. An attacker who captures the unprotected handshake can impersonate the authenticated Windows principal for the SCT lifetime (~10 hours) and decrypt or forge subsequent WS-SecureConversation traffic. No public exploit identified at time of analysis, but the vendor-confirmed advisory (GHSA-2288-8h3r-cqgg) and CVSS 7.4 indicate a meaningful confidentiality/integrity exposure for affected .NET WCF replacement deployments.
Missing encryption of cluster replication traffic in Apache Tomcat 11.0.20, 10.1.53, and 9.0.116 exposes sensitive session data to network-positioned attackers because the EncryptInterceptor - the clustering security control - can be bypassed due to a regression introduced by the fix for CVE-2026-29146. Listed in CISA KEV as actively exploited with a publicly available exploit, though EPSS sits at just 0.01% (1st percentile), indicating targeted rather than widespread automated exploitation. The confidentiality impact is rated High with no integrity or availability impact, consistent with CWE-311 (Missing Encryption of Sensitive Data).
IPv6 Pod traffic in Antrea dual-stack Kubernetes clusters transmits in plaintext despite IPsec encryption configuration, exposing inter-node communication to network eavesdropping. Affects Antrea versions prior to 2.6.0, 2.5.2, and 2.4.5 when dual-stack networking is enabled with trafficEncryptionMode: ipsec. Vendor-released patches are available across multiple stable branches. No public exploit identified at time of analysis, though the vulnerability bypasses intended encryption controls and could enable passive network monitoring in multi-tenant or untrusted network environments.
DSA Study Hub stores JWT authentication tokens in unencrypted HTTP cookies, allowing attackers to extract and replay user credentials to gain unauthorized access to accounts. An unauthenticated remote attacker can intercept these tokens through network traffic analysis or client-side inspection to impersonate legitimate users. A patch is available in commit d527fba and should be applied immediately.
Plaintext token storage in Jenkins Parameterized Remote Trigger Plugin 3.2.2 and earlier exposes authentication tokens to any Jenkins user holding Item/Extended Read permission or to anyone with direct access to the Jenkins controller filesystem. Tokens written to job config.xml files are readable without decryption, potentially allowing lower-privileged users to impersonate legitimate remote-trigger callers and invoke builds on downstream Jenkins instances. No public exploit has been identified; SSVC assessment confirms no active exploitation and a non-automatable attack path.
openssl_encrypt by jahlives (versions before 1.4.9) embeds an unkeyed SHA-256 digest of each plaintext document into the encrypted file's cleartext header, creating a passive plaintext-confirmation oracle. Any party who possesses an encrypted file - including unauthorized recipients of intercepted or leaked archives - can extract this hash without the encryption password and use it to verify guessed or known plaintexts via offline dictionary attacks. Additionally, because the hash is unkeyed and deterministic, identical source documents encrypted separately under different passwords produce matching header hashes, enabling cross-file correlation and fingerprinting that undermines the confidentiality guarantees users expect from file encryption. No public exploit code has been identified at time of analysis, and this vulnerability does not appear in CISA KEV.
Sensitive-file exposure in the openssl-encrypt pip package (openssl_encrypt) at versions <= 1.4.8 stems from its 'Encrypted USB Workspace' feature writing a marker that falsely declares the workspace AES-256-GCM encrypted while the derived key is never applied and the directory remains in cleartext. Users who trust the branding and store files in the workspace leave them fully readable on the removable media, so anyone with physical possession of the USB device can recover the data. No public exploit identified at time of analysis and the flaw is not in CISA KEV, but the failure silently defeats the product's core security promise.
Cleartext exposure of Wi-Fi credentials in DJI consumer and prosumer drones lets an attacker within Bluetooth range recover the drone's Wi-Fi SSID, PSK, and trusted-client UUID by passively sniffing unencrypted DUML-over-BLE messages exchanged during a normal DJI Fly connection or QuickTransfer handoff. This affects a broad range of current DJI models (Neo, Flip, Air 3/3S, Avata 2/360, Mavic 3 family, Mavic 4 Pro, and Mini 2 through Mini 5 Pro) below specific firmware versions. Recovered credentials grant the attacker access to the drone's internal Wi-Fi network and the ability to decrypt the operator's Wi-Fi traffic; no public exploit identified at time of analysis, and it is not listed in CISA KEV.
Unencrypted data transmission in Samsung Smart Switch prior to version 3.7.72.6 exposes sensitive personal data to interception by adjacent network attackers. An attacker positioned on the same network segment can passively capture data flowing between devices during an active Smart Switch wireless transfer session. No public exploit has been identified and no CISA KEV listing exists, but the adjacent-network vector and low attack complexity make this a realistic threat on shared or untrusted Wi-Fi networks.
Missing-encryption weaknesses in Cisco RoomOS software (the OS for Cisco Webex/Room collaboration endpoints) were fixed in an internal-hardening release covering multiple internally discovered issues grouped under CWE-311. Because sensitive data or communications are not adequately encrypted, network-positioned attackers could intercept or expose information handled by affected devices. There is no public exploit identified at time of analysis and this CVE is not in CISA KEV; EPSS is negligible at 0.06% (0th percentile), consistent with SSVC 'Exploitation: none.' Note the published CVSS 9.8 (C:H/I:H/A:H) sits uneasily against a CWE-311/Information-Disclosure classification, which normally implies a confidentiality-centric impact.
Authenticated principal impersonation in CoreWCF (versions >=1.9.0, <1.9.1) occurs because the SPNEGO SecurityContextToken proof key returned in the RequestSecurityTokenResponse (RSTR) is wrapped without confidentiality protection, allowing any on-path observer to recover it. An attacker who captures the unprotected handshake can impersonate the authenticated Windows principal for the SCT lifetime (~10 hours) and decrypt or forge subsequent WS-SecureConversation traffic. No public exploit identified at time of analysis, but the vendor-confirmed advisory (GHSA-2288-8h3r-cqgg) and CVSS 7.4 indicate a meaningful confidentiality/integrity exposure for affected .NET WCF replacement deployments.
Missing encryption of cluster replication traffic in Apache Tomcat 11.0.20, 10.1.53, and 9.0.116 exposes sensitive session data to network-positioned attackers because the EncryptInterceptor - the clustering security control - can be bypassed due to a regression introduced by the fix for CVE-2026-29146. Listed in CISA KEV as actively exploited with a publicly available exploit, though EPSS sits at just 0.01% (1st percentile), indicating targeted rather than widespread automated exploitation. The confidentiality impact is rated High with no integrity or availability impact, consistent with CWE-311 (Missing Encryption of Sensitive Data).
IPv6 Pod traffic in Antrea dual-stack Kubernetes clusters transmits in plaintext despite IPsec encryption configuration, exposing inter-node communication to network eavesdropping. Affects Antrea versions prior to 2.6.0, 2.5.2, and 2.4.5 when dual-stack networking is enabled with trafficEncryptionMode: ipsec. Vendor-released patches are available across multiple stable branches. No public exploit identified at time of analysis, though the vulnerability bypasses intended encryption controls and could enable passive network monitoring in multi-tenant or untrusted network environments.
DSA Study Hub stores JWT authentication tokens in unencrypted HTTP cookies, allowing attackers to extract and replay user credentials to gain unauthorized access to accounts. An unauthenticated remote attacker can intercept these tokens through network traffic analysis or client-side inspection to impersonate legitimate users. A patch is available in commit d527fba and should be applied immediately.
Plaintext token storage in Jenkins Parameterized Remote Trigger Plugin 3.2.2 and earlier exposes authentication tokens to any Jenkins user holding Item/Extended Read permission or to anyone with direct access to the Jenkins controller filesystem. Tokens written to job config.xml files are readable without decryption, potentially allowing lower-privileged users to impersonate legitimate remote-trigger callers and invoke builds on downstream Jenkins instances. No public exploit has been identified; SSVC assessment confirms no active exploitation and a non-automatable attack path.