{"answers":{"affected":"2 open source packages ship an affected version, including devalue.","exploited":"There is no known exploitation of GHSA-33hq-fvwr-56pm in the wild and no public exploit code.","fix":"Upgrade devalue to 5.6.3 or later.","what":"GHSA-33hq-fvwr-56pm is a denial of service vulnerability in devalue, published on 19 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-33hq-fvwr-56pm and fix it if it is affected.\n\nWhat it is: GHSA-33hq-fvwr-56pm is a denial of service vulnerability in devalue, published on 19 Feb 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 GHSA-33hq-fvwr-56pm in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- devalue (npm): affected all versions; fixed in 5.6.3\n- devalue (npm): affected all versions; fixed in 5.6.3\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/GHSA-33hq-fvwr-56pm/ (Markdown: https://insights.sbomify.com/GHSA-33hq-fvwr-56pm/index.md)","id":"GHSA-33hq-fvwr-56pm","markdown":"https://insights.sbomify.com/GHSA-33hq-fvwr-56pm/index.md","name":"GHSA-33hq-fvwr-56pm","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript serialization library","requires_auth":"none","summary":"An attacker could cause server-side CPU and memory exhaustion by triggering serialization of sparse arrays, leading to denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"Under certain circumstances, serializing sparse arrays using `uneval` or `stringify` could cause CPU and/or memory exhaustion. When this occurs on the server, it results in a DoS. This is extremely difficult to take advantage of in practice, as an attacker would have to manage to create a sparse array on the server — which is impossible in every mainstream wire format — and then that sparse array would have to be run through `uneval` or `stringify`.","ecosystems":["npm"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"devalue affected by CPU and memory amplification from sparse arrays","id":"GHSA-33hq-fvwr-56pm","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"npm","fixed":["5.6.3"],"introduced":["0"],"last_affected":[],"package":"devalue","purl":null,"source":"GHSA-33hq-fvwr-56pm"},{"ecosystem":"npm","fixed":["5.6.3"],"introduced":["0"],"last_affected":[],"package":"devalue","purl":"pkg:npm/devalue","source":"GHSA-33hq-fvwr-56pm"}],"products":null,"published":"2026-02-19","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"An attacker could cause server-side CPU and memory exhaustion by triggering serialization of sparse arrays, leading to denial of service.","url":"https://insights.sbomify.com/GHSA-33hq-fvwr-56pm/"}