Monthly
AXIS Camera Station Pro and Camera Station 5 weakly encrypt database backups (CWE-326), so an attacker who obtains a backup file can attack it offline and recover the credentials stored inside. The exposure covers backups created before the fix and the extra recovery backup that Camera Station automatically creates when the update is applied; the CVSS 7.1 vector (AV:L/PR:L, UI:N) means local access to the backup artifacts and low privileges are required, not remote reachability. No public exploit code or confirmed active exploitation was identified at time of analysis, and updating alone does not remove already-exposed backups.
Slican telephone exchanges encrypt their TCP/IP signalling and management traffic with a symmetric key that is hardcoded in multiple firmware binaries, so anyone who obtains a single firmware image or device copy can decrypt that traffic on any installation using the same key. The issue is fixed in IPx series version 6.62.0100; CVSS 4.0 rates it 8.2 with attack prerequisites (AT:P) because exploitation also requires a position to capture the encrypted traffic (passive sniffing or MITM on the exchange's network). Three discontinued models - CCT-1668 (CCT1CPU), MAC-6400 and CXS-0424, discontinued in 2011 and 2012 - remain permanently affected because they cannot receive a software fix and require a hardware upgrade. There is no confirmed active exploitation (not in CISA KEV) and no public exploit identified at time of analysis; the impact is confidentiality-only (high), with no integrity or availability effect.
Imprivata Enterprise Access Management at version 26.2.6 and earlier ships with no capability to rotate the RSA key pair it uses when generating X.509 certificates, so the same static private key can remain in service indefinitely. An attacker cannot exploit this over the network to steal data on its own; the exposure only materializes if that long-lived key is separately obtained through theft, insider access, or eventual cryptanalysis, after which past and future certificate-based trust relationships could be undermined. There is no public exploit identified at time of analysis and no evidence of active exploitation, and EPSS rates the issue at roughly 0.07 percent (0th percentile), consistent with this being a cryptographic lifecycle and hygiene deficiency rather than a directly exploitable remote flaw.
RabbitMQ's amqp091-go Go client library, in all versions before 1.13.0, builds TLS configuration from amqps:// URIs without setting a minimum protocol version, so builds that use a Go runtime permitting TLS 1.0 or 1.1 can negotiate an obsolete protocol. An active man-in-the-middle positioned on the network path could then force a downgrade and weaken the confidentiality and integrity of AMQP traffic, including credentials, though the independently assessed vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N) shows this requires a high degree of attacker positioning plus the legacy-toolchain precondition, and the published 9.4 CVSS 4.0 score overstates real-world exposure for modern deployments. The fix is a two-line MinVersion change shipped in version 1.13.0; no public exploit identified at time of analysis.
Inadequate PBKDF2-HMAC-SHA256 iteration counts in openssl_encrypt versions before 1.4.9 leave post-quantum cryptography keyfile private keys and dual-encryption file-password verification material vulnerable to offline brute-force attack. The library applies only 100,000 iterations for PQC keyfile wrapping and a critically low 10,000 iterations for file-password verification - far below current NIST SP 800-132 recommendations - enabling attackers who obtain keyfiles or encrypted files to recover wrapping passwords using commodity GPU or ASIC hardware at practical cost. No public exploit has been identified at time of analysis, but the attack is technically straightforward once the prerequisite protected material is acquired, and vendor-released patch 1.4.9 is available.
Weak cryptographic key derivation in the openssl_encrypt Python library (all versions before 1.4.0) stems from its key-normalization routines invoking HKDF with no salt and a static info parameter, making derived keys deterministic for identical inputs. This reduces effective entropy and weakens resistance to multi-target (batch) attacks, letting an adversary who collects ciphertexts or derived-key material amortize cryptanalytic effort across many victims. No public exploit identified at time of analysis; the flaw was reported by VulnCheck and a vendor patch is available in 1.4.0.
Remote code execution in IBM Langflow OSS (versions 1.0.0 through 1.10.3) allows authenticated attackers to execute arbitrary Python code by exploiting a cryptographic weakness (CWE-326) in the custom component validation mechanism. When the optional hardening mode is enabled - the feature intended to restrict execution to trusted component templates - the application validates submitted component code against a truncated SHA-256 digest, making it computationally feasible for an attacker to craft a malicious Python file that collides with a trusted template's hash and bypasses the validation gate entirely. No public exploit code has been identified at time of analysis; a vendor patch is available per IBM advisory, though the exact fixed version is not stated in available data.
Bouncy Castle for Java's BKS keystore implementation silently accepted legacy version 0/1 keystores that derive a critically weak 16-bit HMAC integrity key - brute-forceable offline in milliseconds against the 65,536-value keyspace - allowing an attacker who can supply or tamper with a keystore file to forge the integrity MAC, inject rogue trusted certificates, and have the manipulated keystore accepted without error. All bc-java releases before 1.85 and bc-lts-java releases before 2.73.12 are affected. No public exploit code has been identified and this vulnerability does not appear in the CISA KEV catalog at time of analysis.
Credential theft in Pronetiqs/Panduit IntraVUE (versions 3.2.1a14 and prior) stems from the use of a cryptographically weak password hash, allowing an attacker who obtains the stored or transmitted hash to recover or replay administrator credentials via a pass-the-hash attack. The flaw affects the IntraVUE industrial network visualization platform and can yield full administrative access to the console. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, though the vulnerability was coordinated through CISA ICS-CERT (advisory ICSA-26-204-04).
Privilege escalation in ARC Informatique PcVue SCADA/HMI software (all versions prior to 17.0.0) arises because the encryption algorithm protecting user-account configuration in the built-in user directory is cryptographically inadequate (CWE-326). A local attacker with low privileges can decrypt or tamper with the stored account configuration and ultimately obtain privileged access to the PcVue application. No public exploit identified at time of analysis, and it is not listed in CISA KEV; the vendor CVSS 4.0 base score is 8.4 (High).
AXIS Camera Station Pro and Camera Station 5 weakly encrypt database backups (CWE-326), so an attacker who obtains a backup file can attack it offline and recover the credentials stored inside. The exposure covers backups created before the fix and the extra recovery backup that Camera Station automatically creates when the update is applied; the CVSS 7.1 vector (AV:L/PR:L, UI:N) means local access to the backup artifacts and low privileges are required, not remote reachability. No public exploit code or confirmed active exploitation was identified at time of analysis, and updating alone does not remove already-exposed backups.
Slican telephone exchanges encrypt their TCP/IP signalling and management traffic with a symmetric key that is hardcoded in multiple firmware binaries, so anyone who obtains a single firmware image or device copy can decrypt that traffic on any installation using the same key. The issue is fixed in IPx series version 6.62.0100; CVSS 4.0 rates it 8.2 with attack prerequisites (AT:P) because exploitation also requires a position to capture the encrypted traffic (passive sniffing or MITM on the exchange's network). Three discontinued models - CCT-1668 (CCT1CPU), MAC-6400 and CXS-0424, discontinued in 2011 and 2012 - remain permanently affected because they cannot receive a software fix and require a hardware upgrade. There is no confirmed active exploitation (not in CISA KEV) and no public exploit identified at time of analysis; the impact is confidentiality-only (high), with no integrity or availability effect.
Imprivata Enterprise Access Management at version 26.2.6 and earlier ships with no capability to rotate the RSA key pair it uses when generating X.509 certificates, so the same static private key can remain in service indefinitely. An attacker cannot exploit this over the network to steal data on its own; the exposure only materializes if that long-lived key is separately obtained through theft, insider access, or eventual cryptanalysis, after which past and future certificate-based trust relationships could be undermined. There is no public exploit identified at time of analysis and no evidence of active exploitation, and EPSS rates the issue at roughly 0.07 percent (0th percentile), consistent with this being a cryptographic lifecycle and hygiene deficiency rather than a directly exploitable remote flaw.
RabbitMQ's amqp091-go Go client library, in all versions before 1.13.0, builds TLS configuration from amqps:// URIs without setting a minimum protocol version, so builds that use a Go runtime permitting TLS 1.0 or 1.1 can negotiate an obsolete protocol. An active man-in-the-middle positioned on the network path could then force a downgrade and weaken the confidentiality and integrity of AMQP traffic, including credentials, though the independently assessed vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N) shows this requires a high degree of attacker positioning plus the legacy-toolchain precondition, and the published 9.4 CVSS 4.0 score overstates real-world exposure for modern deployments. The fix is a two-line MinVersion change shipped in version 1.13.0; no public exploit identified at time of analysis.
Inadequate PBKDF2-HMAC-SHA256 iteration counts in openssl_encrypt versions before 1.4.9 leave post-quantum cryptography keyfile private keys and dual-encryption file-password verification material vulnerable to offline brute-force attack. The library applies only 100,000 iterations for PQC keyfile wrapping and a critically low 10,000 iterations for file-password verification - far below current NIST SP 800-132 recommendations - enabling attackers who obtain keyfiles or encrypted files to recover wrapping passwords using commodity GPU or ASIC hardware at practical cost. No public exploit has been identified at time of analysis, but the attack is technically straightforward once the prerequisite protected material is acquired, and vendor-released patch 1.4.9 is available.
Weak cryptographic key derivation in the openssl_encrypt Python library (all versions before 1.4.0) stems from its key-normalization routines invoking HKDF with no salt and a static info parameter, making derived keys deterministic for identical inputs. This reduces effective entropy and weakens resistance to multi-target (batch) attacks, letting an adversary who collects ciphertexts or derived-key material amortize cryptanalytic effort across many victims. No public exploit identified at time of analysis; the flaw was reported by VulnCheck and a vendor patch is available in 1.4.0.
Remote code execution in IBM Langflow OSS (versions 1.0.0 through 1.10.3) allows authenticated attackers to execute arbitrary Python code by exploiting a cryptographic weakness (CWE-326) in the custom component validation mechanism. When the optional hardening mode is enabled - the feature intended to restrict execution to trusted component templates - the application validates submitted component code against a truncated SHA-256 digest, making it computationally feasible for an attacker to craft a malicious Python file that collides with a trusted template's hash and bypasses the validation gate entirely. No public exploit code has been identified at time of analysis; a vendor patch is available per IBM advisory, though the exact fixed version is not stated in available data.
Bouncy Castle for Java's BKS keystore implementation silently accepted legacy version 0/1 keystores that derive a critically weak 16-bit HMAC integrity key - brute-forceable offline in milliseconds against the 65,536-value keyspace - allowing an attacker who can supply or tamper with a keystore file to forge the integrity MAC, inject rogue trusted certificates, and have the manipulated keystore accepted without error. All bc-java releases before 1.85 and bc-lts-java releases before 2.73.12 are affected. No public exploit code has been identified and this vulnerability does not appear in the CISA KEV catalog at time of analysis.
Credential theft in Pronetiqs/Panduit IntraVUE (versions 3.2.1a14 and prior) stems from the use of a cryptographically weak password hash, allowing an attacker who obtains the stored or transmitted hash to recover or replay administrator credentials via a pass-the-hash attack. The flaw affects the IntraVUE industrial network visualization platform and can yield full administrative access to the console. There is no public exploit identified at time of analysis and it is not listed in CISA KEV, though the vulnerability was coordinated through CISA ICS-CERT (advisory ICSA-26-204-04).
Privilege escalation in ARC Informatique PcVue SCADA/HMI software (all versions prior to 17.0.0) arises because the encryption algorithm protecting user-account configuration in the built-in user directory is cryptographically inadequate (CWE-326). A local attacker with low privileges can decrypt or tamper with the stored account configuration and ultimately obtain privileged access to the PcVue application. No public exploit identified at time of analysis, and it is not listed in CISA KEV; the vendor CVSS 4.0 base score is 8.4 (High).