CVE-2026-8881

CVE-2026-8881 is a high-severity vulnerability in Securly with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Description

Version 3.0.7 of the Securly Chrome Extension uses EVP_BytesToKey key derivation with MD5 and a single iteration for AES encryption. MD5 has been broken since 2004 and a single iteration provides no key stretching.

Frequently asked questions

What is CVE-2026-8881?
Version 3.0.7 of the Securly Chrome Extension uses EVP_BytesToKey key derivation with MD5 and a single iteration for AES encryption. MD5 has been broken since 2004 and a single iteration provides no key stretching.
How severe is CVE-2026-8881?
CVE-2026-8881 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2026-8881 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (6th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-8881?
CVE-2026-8881 affects Securly. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-8881?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2026-8881 have an EU (EUVD) identifier?
Yes. CVE-2026-8881 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-34166.
When was CVE-2026-8881 published?
CVE-2026-8881 was published on 2026-06-03 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Securly

All CVEs affecting Securly →