{"answers":{"affected":"2 open source packages ship an affected version, including @evomap/evolver.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42077 exists.","fix":"Upgrade @evomap/evolver to 1.69.3 or later.","what":"CVE-2026-42077 is a medium-severity code injection vulnerability in EvoMap evolver, published on 4 May 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-42077 and fix it if it is affected.\n\nWhat it is: CVE-2026-42077 is a medium-severity code injection vulnerability in EvoMap evolver, published on 4 May 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-42077 exists.\n\nAffected packages and fixed versions:\n- @evomap/evolver (npm): affected all versions; fixed in 1.69.3\n- @evomap/evolver (npm): affected all versions; fixed in 1.69.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/CVE-2026-42077/ (Markdown: https://insights.sbomify.com/CVE-2026-42077/index.md)","id":"CVE-2026-42077","markdown":"https://insights.sbomify.com/CVE-2026-42077/index.md","name":"CVE-2026-42077","record":{"aliases":["GHSA-2cjr-5v3h-v2w4"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"AI agent engine","requires_auth":"high_privilege","summary":"Attackers can achieve code execution by injecting malicious properties into Object.prototype via unfiltered user data in mailbox store operations.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.2,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:H","version":"3.1"},"cwes":[{"id":"CWE-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"}],"description":"Evolver is a GEP-powered self-evolving engine for AI agents. Prior to version 1.69.3, a prototype pollution vulnerability in the mailbox store module allows attackers to modify the behavior of all JavaScript objects by injecting malicious properties into Object.prototype. The vulnerability exists in the _applyUpdate() and _updateRecord() functions which use Object.assign() to merge user-controlled data without filtering dangerous keys like __proto__, constructor, or prototype. This issue has been patched in version 1.69.3.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Evolver: Prototype Pollution via `Object.assign()` in mailbox store operations","id":"CVE-2026-42077","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"PPTAgent: Arbitrary File Write + Directory Creation via markdown_table_to_image","id":"CVE-2026-42078"},"packages":[{"ecosystem":"npm","fixed":["1.69.3"],"introduced":["0"],"last_affected":[],"package":"@evomap/evolver","purl":null,"source":"GHSA-2cjr-5v3h-v2w4"},{"ecosystem":"npm","fixed":["1.69.3"],"introduced":["0"],"last_affected":[],"package":"@evomap/evolver","purl":"pkg:npm/%40evomap/evolver","source":"GHSA-2cjr-5v3h-v2w4"}],"prev":{"headline":"Evolver: Command Injection via `execSync` in `_extractLLM()` function allows Remote Code Execution","id":"CVE-2026-42076"},"products":["evolver"],"published":"2026-05-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-05-06","vendors":["EvoMap"]},"summary":"Attackers can achieve code execution by injecting malicious properties into Object.prototype via unfiltered user data in mailbox store operations.","url":"https://insights.sbomify.com/CVE-2026-42077/"}