{"answers":{"affected":"1 open source package ship an affected version, including ash_typescript.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-105283 exists.","fix":"Upgrade ash_typescript to 0.19.1 or later.","what":"CVE-2026-105283 is a medium-severity vulnerability in ash-project ash_typescript, published on 12 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-105283 and fix it if it is affected.\n\nWhat it is: CVE-2026-105283 is a medium-severity vulnerability in ash-project ash_typescript, published on 12 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-105283 exists.\n\nAffected packages and fixed versions:\n- ash_typescript (Hex): affected from 0.1.0; fixed in 0.19.1\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-105283/ (Markdown: https://insights.sbomify.com/CVE-2026-105283/index.md)","id":"CVE-2026-105283","markdown":"https://insights.sbomify.com/CVE-2026-105283/index.md","name":"CVE-2026-105283","record":{"aliases":["EEF-CVE-2026-105283","GHSA-7gxc-w225-f7f3"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Elixir TypeScript RPC library","requires_auth":"none","summary":"An unauthenticated attacker can read internal Elixir terms from RPC error responses by triggering specific errors in the ash_typescript library.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/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-209","name":"Generation of Error Message Containing Sensitive Information"}],"description":"Generation of Error Message Containing Sensitive Information vulnerability in ash-project ash_typescript allows an unauthenticated attacker to read internal Elixir terms from an RPC error response by provoking an error the error builder has no dedicated clause for.\n\nAshTypescript.Rpc.ErrorBuilder.build_error_response/1 in lib/ash_typescript/rpc/error_builder.ex renders a pipeline error term that matches no specific clause with inspect/1 and places the result in details.error of the client-facing error. Ash exceptions take a separate path in AshTypescript.Rpc.Errors where unhandled cases are redacted behind an errorId, but these fallbacks have no redaction, so whatever the term carries reaches the HTTP or channel response. Two request paths hand it such terms: a struct-typed action argument with an invalid nested value, where cast_map_to_struct/2 in lib/ash_typescript/rpc/input_formatter.ex throws the raw Ash.Type cast error into the builder, and field selection on a generic action that returns a primitive, where format_field_type/1 inspects the full Ash.Info.Manifest.Type struct into vars.returnType. Resource module names in vars.resource are not treated as sensitive and are out of scope.\n\nThis issue affects ash_typescript: from 0.1.0 before 0.19.1.","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":"Internal error terms inspected into AshTypescript RPC error responses","id":"CVE-2026-105283","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":1,"n_references":5,"next":{"headline":"Totolink A3002MU Authentication Check boa sub_40FCFC improper authorization","id":"CVE-2026-105284"},"packages":[{"ecosystem":"Hex","fixed":["0.19.1"],"introduced":["0.1.0"],"last_affected":[],"package":"ash_typescript","purl":"pkg:hex/ash_typescript","source":"EEF-CVE-2026-105283"}],"prev":{"headline":"Grid Protection Alliance openPDC and openHistorian Missing Authentication for Critical Function","id":"CVE-2026-105281"},"products":["ash_typescript"],"published":"2026-10-12","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-16","vendors":["ash-project"]},"summary":"An unauthenticated attacker can read internal Elixir terms from RPC error responses by triggering specific errors in the ash_typescript library.","url":"https://insights.sbomify.com/CVE-2026-105283/"}