{"answers":{"affected":"3 open source packages ship an affected version, including mesop.","exploited":"There is no known exploitation of CVE-2025-30358 in the wild and no public exploit code.","fix":"Upgrade mesop to 0.14.1 or later.","what":"CVE-2025-30358 is a high-severity code injection vulnerability in mesop-dev mesop, published on 27 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-30358 and fix it if it is affected.\n\nWhat it is: CVE-2025-30358 is a high-severity code injection vulnerability in mesop-dev mesop, published on 27 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-30358 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- mesop (PyPI): affected all versions; fixed in 0.14.1\n- mesop (PyPI): affected all versions; fixed in 0.14.1\n- mesop (PyPI): affected all versions; fixed in 0.14.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-2025-30358/ (Markdown: https://insights.sbomify.com/CVE-2025-30358/index.md)","id":"CVE-2025-30358","markdown":"https://insights.sbomify.com/CVE-2025-30358/index.md","name":"CVE-2025-30358","record":{"aliases":["GHSA-f3mf-hm6v-jfhh","PYSEC-2026-1624"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Python UI framework","requires_auth":"low_privilege","summary":"Attackers can pollute classes to cause denial of service, impersonate roles, or potentially execute code in Mesop applications.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-915","name":"Improperly Controlled Modification of Dynamically-Determined Object Attributes"}],"description":"Mesop is a Python-based UI framework that allows users to build web applications. A class pollution vulnerability in Mesop prior to version 0.14.1 allows attackers to overwrite global variables and class attributes in certain Mesop modules during runtime. This vulnerability could directly lead to a denial of service (DoS) attack against the server. Additionally, it could also result in other severe consequences given the application's implementation, such as identity confusion, where an attacker could impersonate an assistant or system role within conversations. This impersonation could potentially enable jailbreak attacks when interacting with large language models (LLMs). Just like the Javascript's prototype pollution, this vulnerability could leave a way for attackers to manipulate the intended data-flow or control-flow of the application at runtime and lead to severe consequences like remote code execution when gadgets are available. Users should upgrade to version 0.14.1 to obtain a fix for the issue.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Mesop Class Pollution vulnerability leads to DoS and Jailbreak attacks","id":"CVE-2025-30358","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"code_injection","year":"2025"},"n_packages":3,"n_references":2,"next":{"headline":"webpack-dev-server users' source code may be stolen when they access a malicious web site","id":"CVE-2025-30359"},"packages":[{"ecosystem":"PyPI","fixed":["0.14.1"],"introduced":["0"],"last_affected":[],"package":"mesop","purl":null,"source":"GHSA-f3mf-hm6v-jfhh"},{"ecosystem":"PyPI","fixed":["0.14.1"],"introduced":["0"],"last_affected":[],"package":"mesop","purl":"pkg:pypi/mesop","source":"GHSA-f3mf-hm6v-jfhh"},{"ecosystem":"PyPI","fixed":["0.14.1"],"introduced":["0"],"last_affected":[],"package":"mesop","purl":"pkg:pypi/mesop","source":"PYSEC-2026-1624"}],"prev":{"headline":"NamelessMC Forum Topic Deletion Triggered by Unrelated User Deletion","id":"CVE-2025-30357"},"products":["mesop"],"published":"2025-03-27","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":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-27","vendors":["mesop-dev"]},"summary":"Attackers can pollute classes to cause denial of service, impersonate roles, or potentially execute code in Mesop applications.","url":"https://insights.sbomify.com/CVE-2025-30358/"}