CVE-2026-8878
Description
Securly Chrome Extension 3.0.7 exposes sensitive SHA-1 hashes via publicly accessible endpoints, allowing unauthenticated access after simple decryption.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Securly Chrome Extension 3.0.7 exposes sensitive SHA-1 hashes via publicly accessible endpoints, allowing unauthenticated access after simple decryption.
Vulnerability
Version 3.0.7 of the Securly Chrome Extension contains multiple publicly accessible endpoints that allow unauthenticated access to sensitive data. The exposed information includes SHA-1 hashes that are obfuscated using a simple Caesar cipher, which can be easily reversed to recover the original hash values and access protected data [1].
Exploitation
An unauthenticated attacker can access publicly available endpoints to retrieve obfuscated SHA-1 hashes. The Caesar cipher used for obfuscation is trivial to reverse, allowing the attacker to recover the original hash values and subsequently access the protected data [1].
Impact
An attacker can gain unauthenticated access to sensitive data by reversing the obfuscated SHA-1 hashes. This could lead to the exposure of configuration information, manipulation of content blocking rules, or potentially other sensitive data depending on what the hashes protect [1].
Mitigation
Not yet disclosed in the available references. The affected version is 3.0.7 [1].
AI Insight generated on Jun 3, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1- Range: <=3.0.7
Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
1News mentions
0No linked articles in our index yet.