ZDF
Sign inSign up

Vulnerabilities

Vulnerability · 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.

Published Jun 3, 2026 · catalog updated Jul 22, 2026 · Version 3.0.7 of the

Check if you run it

No confirmed exploitation is on record for CVE-2026-8881. EPSS is 0.20%. Act only if a listed version of Version 3.0.7 of the is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Version 3.0.7 of the).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.20%
Remediation
Advisory link
Affected products
cpe securly/securly

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe securly/securly3.0.7

How to fix CVE-2026-8881

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-8881. EPSS is 0.20%. Act only if a listed version of Version 3.0.7 of the is installed.

Which versions are affected?

Compare what you have installed with 3.0.7. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 0.20%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Jun 3, 2026 · NIST NVD

    Detected

    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.

  2. Jul 22, 2026 · NIST NVD

    Updated

    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.

Sources

  • CVE.orgVulnerability recordCVE-2026-8881

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-8881

    30-day exploitation probability 0.2%

    first.org
  • NIST NVDVulnerability recordCVE-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.

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.