CVE-2026-8881: Securly Chrome Extension Weak Crypto Flaw

CVE-2026-8881 Overview

CVE-2026-8881 affects version 3.0.7 of the Securly Chrome Extension. The extension derives AES encryption keys using EVP_BytesToKey with the MD5 hash function and a single iteration. MD5 has been cryptographically broken since 2004, and a single iteration provides no meaningful key stretching against brute-force or dictionary attacks. This weak key derivation undermines the confidentiality of any data the extension encrypts. The flaw is documented in the CERT Vulnerability Advisory.

Critical Impact

Attackers who obtain ciphertext produced by the extension can recover encryption keys and decrypt protected data with low computational cost.

Affected Products

• Securly Chrome Extension version 3.0.7

Discovery Timeline

• 2026-06-03 - CVE-2026-8881 published to NVD
• 2026-06-03 - Last updated in NVD database

Technical Details for CVE-2026-8881

Vulnerability Analysis

The Securly Chrome Extension uses OpenSSL's legacy EVP_BytesToKey routine to derive AES keys from a password or passphrase. This function combines a hash algorithm with an iteration count to produce key material. In version 3.0.7, the implementation specifies MD5 as the hash and uses a single iteration. Modern guidance requires key derivation functions such as PBKDF2, scrypt, or Argon2 with tens of thousands of iterations or memory-hard parameters. The combination of a broken hash and no stretching makes the derived key recoverable through offline attacks. This vulnerability falls under the weak cryptography category [CWE-327] and weak key derivation [CWE-916].

Root Cause

The root cause is the use of EVP_BytesToKey with MD5 and an iteration count of one. MD5 produces predictable collisions and offers no resistance to preimage or brute-force attacks on low-entropy inputs. Without iteration, an attacker with a password candidate list can test millions of guesses per second on commodity hardware.

Attack Vector

An attacker who captures encrypted blobs generated by the extension — from local storage, network traffic, or backups — can perform an offline dictionary or brute-force attack against the key derivation. Once the key is recovered, the attacker decrypts all data protected by the same passphrase. Detailed exploitation specifics are described in the CERT Vulnerability Advisory.

// No verified exploit code is published.
// See the CERT advisory for technical details on the weak
// EVP_BytesToKey(MD5, iter=1) construction used by the extension.

Detection Methods for CVE-2026-8881

Indicators of Compromise

• Presence of Securly Chrome Extension version 3.0.7 in browser extension inventories.
• Encrypted artifacts produced by the extension that exhibit the OpenSSL Salted__ header characteristic of EVP_BytesToKey output.

Detection Strategies

• Inventory Chrome extensions across managed endpoints and flag any installation matching the affected version.
• Audit application binaries and source for calls to EVP_BytesToKey paired with MD5 to identify similar weak constructions in other software.
• Review stored ciphertext for the Salted__ magic bytes that indicate use of the legacy OpenSSL key derivation routine.

Monitoring Recommendations

• Monitor browser extension installation events and version changes through endpoint management tooling.
• Track outbound transmissions of encrypted payloads originating from browser extension processes.
• Alert on extension auto-update failures that may leave users pinned to the vulnerable version.

How to Mitigate CVE-2026-8881

Immediate Actions Required

• Identify endpoints running Securly Chrome Extension version 3.0.7 and restrict its use until a fixed release is deployed.
• Treat any data previously encrypted by the affected version as potentially compromised and rotate associated secrets.
• Consult the CERT Vulnerability Advisory for vendor status and updated guidance.

Patch Information

No patch details are listed in the published NVD record. Administrators should monitor the vendor's release channel and the CERT Vulnerability Advisory for a fixed version that replaces EVP_BytesToKey with a modern key derivation function such as PBKDF2, scrypt, or Argon2.

Workarounds

• Block installation of the affected extension version through Chrome enterprise policy until a corrected release is available.
• Avoid relying on the extension's encryption to protect sensitive data, and apply transport-layer or storage-layer encryption with vetted libraries instead.
• Re-encrypt sensitive material using a key derived through PBKDF2, scrypt, or Argon2 with appropriate parameters.

# Example Chrome enterprise policy to block a specific extension ID
# Replace <EXTENSION_ID> with the Securly extension identifier
cat <<'EOF' > /etc/opt/chrome/policies/managed/block_securly.json
{
  "ExtensionInstallBlocklist": ["<EXTENSION_ID>"]
}
EOF