{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-8878 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-8878 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-8878 is a high-severity vulnerability in Securly Chrome Extension, published on 3 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-8878 and fix it if it is affected.\n\nWhat it is: CVE-2026-8878 is a high-severity vulnerability in Securly Chrome Extension, published on 3 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-8878 in the wild and no public exploit code.\n\nAffected product: Securly Chrome Extension. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-8878/ (Markdown: https://insights.sbomify.com/CVE-2026-8878/index.md)","id":"CVE-2026-8878","markdown":"https://insights.sbomify.com/CVE-2026-8878/index.md","name":"CVE-2026-8878","record":{"aliases":["GHSA-wwcp-6f37-8chw"],"analysis":{"component_type":"browser","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Securly Chrome Extension","requires_auth":"none","summary":"Unauthenticated attackers can access sensitive data via exposed endpoints in the Securly Chrome Extension due to weak obfuscation of SHA-1 hashes.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"certcc","cpe":[{"product":"securly","vendor":"securly"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-326","name":"Inadequate Encryption Strength"}],"description":"Version 3.0.7 of the Securly Chrome Extension exposes multiple publicly accessible endpoints that allow unauthenticated access to sensitive data. The exposed information consists of SHA-1 hashes that are inadequately obfuscated using a simple Caesar cipher, which can be easily reversed to recover the original hash values and access the protected data.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"CVE-2026-8878","id":"CVE-2026-8878","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"CVE-2026-8879","id":"CVE-2026-8879"},"packages":[],"prev":{"headline":"Responsive Video Embedder \u003c= 0.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode Attributes","id":"CVE-2026-8877"},"products":["Securly Chrome Extension"],"published":"2026-06-03","related":[{"cvss_score":7.5,"headline":"CVE-2026-8879","id":"CVE-2026-8879","kev_date_added":null,"published":"2026-06-03"},{"cvss_score":7.5,"headline":"CVE-2026-8881","id":"CVE-2026-8881","kev_date_added":null,"published":"2026-06-03"},{"cvss_score":7.5,"headline":"CVE-2026-8888","id":"CVE-2026-8888","kev_date_added":null,"published":"2026-06-03"},{"cvss_score":7.5,"headline":"CVE-2026-8889","id":"CVE-2026-8889","kev_date_added":null,"published":"2026-06-03"},{"cvss_score":7.3,"headline":"CVE-2026-8876","id":"CVE-2026-8876","kev_date_added":null,"published":"2026-06-03"},{"cvss_score":7.1,"headline":"CVE-2026-8874","id":"CVE-2026-8874","kev_date_added":null,"published":"2026-06-03"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-04","vendors":["Securly"]},"summary":"Unauthenticated attackers can access sensitive data via exposed endpoints in the Securly Chrome Extension due to weak obfuscation of SHA-1 hashes.","url":"https://insights.sbomify.com/CVE-2026-8878/"}