{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46803 exists.","fix":"Apply the vendor's patch.","what":"CVE-2025-46803 is a medium-severity vulnerability, published on 26 May 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-46803 and fix it if it is affected.\n\nWhat it is: CVE-2025-46803 is a medium-severity vulnerability, published on 26 May 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-46803 exists.\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-46803/ (Markdown: https://insights.sbomify.com/CVE-2025-46803/index.md)","id":"CVE-2025-46803","markdown":"https://insights.sbomify.com/CVE-2025-46803/index.md","name":"CVE-2025-46803","record":{"aliases":["ALPINE-CVE-2025-46803","BELL-CVE-2025-46803","GHSA-g2cq-wg23-g8qw"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["data_modify","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"GNU Screen terminal","requires_auth":"low_privilege","summary":"Screen allocates world-writable PTYs by default, allowing local attackers to inject input into other users' sessions.","user_interaction":"required","vuln_class":"misconfiguration"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"suse","cpe":[],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:A/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-276","name":"Incorrect Default Permissions"}],"description":"The default mode of pseudo terminals (PTYs) allocated by Screen was changed from 0620 to 0622, thereby allowing anyone to write to any Screen PTYs in the system.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Screen creates by default world-writable PTYs","id":"CVE-2025-46803","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"misconfiguration","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Screen 5.0.0 and older versions allow file existence tests when installed setuid-root","id":"CVE-2025-46804"},"packages":[],"prev":{"headline":"Temporary chown() of users' TTY to mode 0666 allows PTY hijacking in screen","id":"CVE-2025-46802"},"products":[],"published":"2025-05-26","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"2025-05-27","vendors":[]},"summary":"Screen allocates world-writable PTYs by default, allowing local attackers to inject input into other users' sessions.","url":"https://insights.sbomify.com/CVE-2025-46803/"}