{"answers":{"affected":"1 open source package ship an affected version, including cloak.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-95105 exists.","fix":"No fix has been published for CVE-2026-95105 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-95105 is a high-severity vulnerability in danielberkompas cloak, published on 6 Oct 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-95105 and fix it if it is affected.\n\nWhat it is: CVE-2026-95105 is a high-severity vulnerability in danielberkompas cloak, published on 6 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-95105 exists.\n\nAffected packages and fixed versions:\n- cloak (Hex): affected from 0.1.0-pre; no fix listed\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-95105/ (Markdown: https://insights.sbomify.com/CVE-2026-95105/index.md)","id":"CVE-2026-95105","markdown":"https://insights.sbomify.com/CVE-2026-95105/index.md","name":"CVE-2026-95105","record":{"aliases":["EEF-CVE-2026-95105","GHSA-hxq7-6hm2-6wvg"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Elixir encryption library","requires_auth":"none","summary":"Attackers with write access to stored ciphertext can forge plaintext values via bit flipping due to missing integrity checks in the Cloak AES-CTR implementation.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-649","name":"Reliance on Obfuscation or Encryption of Security-Relevant Inputs without Integrity Checking"}],"description":"Reliance on Obfuscation or Encryption of Security-Relevant Inputs without Integrity Checking vulnerability in danielberkompas cloak allows an attacker with write access to stored ciphertext to make it decrypt to a chosen value via bit flipping.\n\nCloak.Ciphers.AES.CTR encrypts with AES-256 in CTR mode and stores the key tag, the IV and the ciphertext with no MAC. decrypt/2 checks only the key tag and the minimum length before it returns the plaintext, and Cloak.Ciphers.Deprecated.AES.CTR decrypts the legacy format the same way. CTR is a stream cipher, so a value XORed into the stored ciphertext is XORed into the plaintext at the same offset. An attacker who can write to the encrypted store (for example through SQL injection or a compromised replica) and who knows or can guess a stored plaintext can replace it with any value of the same length. The application receives that value with no error.\n\nThis issue affects cloak: from 0.1.0-pre onward.","ecosystems":["Hex"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Cloak AES-CTR cipher lacks ciphertext authentication, allowing chosen-plaintext forgery by bit flipping","id":"CVE-2026-95105","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"weak_cryptography","year":"2026"},"n_packages":1,"n_references":3,"next":{"headline":"Gitea review and execution mismatch through duplicate tree entries","id":"CVE-2026-95106"},"packages":[{"ecosystem":"Hex","fixed":[],"introduced":["0.1.0-pre"],"last_affected":[],"package":"cloak","purl":"pkg:hex/cloak","source":"EEF-CVE-2026-95105"}],"prev":{"headline":"Memory corruption in WEX-G300","id":"CVE-2026-95104"},"products":["cloak"],"published":"2026-10-06","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Erlang Ecosystem Foundation","prefix":"EEF"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-06","vendors":["danielberkompas"]},"summary":"Attackers with write access to stored ciphertext can forge plaintext values via bit flipping due to missing integrity checks in the Cloak AES-CTR implementation.","url":"https://insights.sbomify.com/CVE-2026-95105/"}