{"answers":{"affected":"1 open source package ship an affected version, including ash_cloak.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-81322 exists.","fix":"Upgrade ash_cloak to 0.4.0 or later.","what":"CVE-2026-81322 is a low-severity vulnerability in ash-project ash_cloak, published on 30 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-81322 and fix it if it is affected.\n\nWhat it is: CVE-2026-81322 is a low-severity vulnerability in ash-project ash_cloak, published on 30 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-81322 exists.\n\nAffected packages and fixed versions:\n- ash_cloak (Hex): affected from 0.1.0; fixed in 0.4.0\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-81322/ (Markdown: https://insights.sbomify.com/CVE-2026-81322/index.md)","id":"CVE-2026-81322","markdown":"https://insights.sbomify.com/CVE-2026-81322/index.md","name":"CVE-2026-81322","record":{"aliases":["EEF-CVE-2026-81322","GHSA-qp4v-vvrg-8ggx"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Elixir encryption library","requires_auth":"none","summary":"Attackers with log or error access can recover plaintext from encrypted fields due to missing sensitive flags in AshCloak action arguments.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"cvss":{"score":2.1,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Exposure of Sensitive Information to an Unauthorized Actor vulnerability in ash-project ash_cloak allows anyone with access to logs, error trackers, or crash reports, or anyone who can trigger a validation error, to recover the plaintext of a field the library encrypts.\n\nAshCloak.Transformers.SetUpEncryption removes each cloaked attribute from the action's accept list and adds an action argument that carries the plaintext into the encryption change. That argument is built with sensitive?: attr.sensitive?, inheriting the flag from the source attribute, so a cloaked attribute declared without sensitive? true produces a non-sensitive argument. It is the only place the cleartext value lives, and the one place Ash will not redact: it appears verbatim in inspect(changeset), Ash.Error.Invalid and validation error messages, telemetry, :sys dumps, and error-tracker payloads. The generated encrypted attribute and decrypt calculation are already hardcoded sensitive.\n\nThis issue affects ash_cloak: from 0.1.0 before 0.4.0.","ecosystems":["Hex"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Cloaked plaintext leaks through a non-sensitive action argument in AshCloak","id":"CVE-2026-81322","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":1,"n_references":4,"next":{"headline":"Hardcoded credentials in QND Advance","id":"CVE-2026-81326"},"packages":[{"ecosystem":"Hex","fixed":["0.4.0"],"introduced":["0.1.0"],"last_affected":[],"package":"ash_cloak","purl":"pkg:hex/ash_cloak","source":"EEF-CVE-2026-81322"}],"prev":{"headline":"CareCam CM2507 Cleartext Storage of Sensitive Information","id":"CVE-2026-81321"},"products":["ash_cloak"],"published":"2026-08-30","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-09-01","vendors":["ash-project"]},"summary":"Attackers with log or error access can recover plaintext from encrypted fields due to missing sensitive flags in AshCloak action arguments.","url":"https://insights.sbomify.com/CVE-2026-81322/"}