openssl_encrypt versions before 1.4.0 contain a vulnerability in PublicKeyBundle.from_dict() that creates key bundles from untrusted data without verifying signatures. Attackers can call from_dict() followed by to_identity() without signature verification to encrypt data using attacker-controlled public keys, leaking secrets.
Casky was already ahead
This CVE exploits attack patterns that Casky's 0matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.
CVE-2026-74876 is a critical deserialization vulnerability in openssl_encrypt that allows attackers to inject malicious public keys into key bundles without cryptographic verification. The vulnerability exists in the PublicKeyBundle.from_dict() method, which reconstructs key objects from untrusted data—such as configuration files, API responses, or inter-service messages—without validating signatures. An attacker can exploit this by crafting a malicious dictionary that defines a public key bundle, then calling to_identity() to establish trust relationships based on unsigned data. This enables attackers to replace legitimate recipient public keys with their own, allowing them to intercept and decrypt encrypted secrets meant for other parties. Any application using openssl_encrypt versions before 1.4.0 that deserializes key bundles from external sources is affected, making this a systemic risk across infrastructure relying on this library for encrypted communication.
While this CVE lacks mapped MITRE ATT&CK techniques, Casky's extended reasoning capabilities would flag this attack pattern by detecting the absence of cryptographic verification in key management workflows. Practitioners using Casky would see findings related to "Insecure Deserialization" (CWE-347) alongside behavioral indicators of "Credential Access" and "Lateral Movement" tactics—specifically the suspicious instantiation of PublicKeyBundle objects without signature validation checks, followed by immediate calls to trust-establishing methods. The platform would highlight code patterns where from_dict() is called on untrusted input sources, drawing connections to potential data exfiltration scenarios. Casky's skill mapping would recommend immediate patching to 1.4.0+, code review of all deserialization points, and implementation of cryptographic verification checks before accepting any key bundle data in production systems.
Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →
Casky has 0 skills that investigate the attack patterns behind CVE-2026-74876. Run one and get CVSS-scored findings in 3 minutes.
Run the skill that detects this →© 2026 Casky.AI, Inc. · AI Security Investigation