{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-8672 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-8672 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-8672 is a medium-severity vulnerability in Gimp Gimp, published on 11 Aug 2025. 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-2025-8672 and fix it if it is affected.\n\nWhat it is: CVE-2025-8672 is a medium-severity vulnerability in Gimp Gimp, published on 11 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-8672 in the wild and no public exploit code.\n\nAffected product: Gimp Gimp. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-8672/ (Markdown: https://insights.sbomify.com/CVE-2025-8672/index.md)","id":"CVE-2025-8672","markdown":"https://insights.sbomify.com/CVE-2025-8672/index.md","name":"CVE-2025-8672","record":{"aliases":["GHSA-rr35-3558-wvf9"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"GIMP image editor","requires_auth":"low_privilege","summary":"Local attackers can bypass macOS TCC privacy protections by using GIMP's bundled Python interpreter to access protected files without user prompts.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CERT-PL","cpe":[{"product":"gimp","vendor":"gimp"}],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-276","name":"Incorrect Default Permissions"}],"description":"MacOS version of GIMP bundles a Python interpreter that inherits the Transparency, Consent, and Control (TCC) permissions\ngranted by the user to the main application bundle. An attacker with local user access can\ninvoke this interpreter with arbitrary commands or scripts, leveraging the\napplication's previously granted TCC permissions to access user's files in privacy-protected folders without triggering user prompts. Accessing other resources beyond previously granted TCC permissions will prompt the user for approval in the name of GIMP, potentially disguising attacker's malicious intent.\n\nThis issue has been fixed in 3.1.4.2 version of GIMP.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"TCC Bypass via Inherited Permissions in Bundled Interpreter in GIMP.app","id":"CVE-2025-8672","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"gimp:gimp","products":["gimp:gimp"],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"AI SEO Link Advisor - Less critical - Server-side Request Forgery - SA-CONTRIB-2025-095","id":"CVE-2025-8675"},"packages":[],"prev":{"headline":"CVE-2025-8671","id":"CVE-2025-8671"},"products":["GIMP"],"published":"2025-08-11","related":[{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2010-4541","kev_date_added":null,"published":"2011-01-07"},{"cvss_score":9.3,"headline":"Integer overflow in n/a","id":"CVE-2009-3909","kev_date_added":null,"published":"2009-11-19"},{"cvss_score":9.3,"headline":"Integer overflow in n/a","id":"CVE-2009-1570","kev_date_added":null,"published":"2009-11-13"},{"cvss_score":9.3,"headline":"Integer overflow in n/a","id":"CVE-2009-0723","kev_date_added":null,"published":"2009-03-23"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2009-0733","kev_date_added":null,"published":"2009-03-23"},{"cvss_score":9.1,"headline":"Race condition in n/a","id":"CVE-2018-12713","kev_date_added":null,"published":"2018-06-24"},{"cvss_score":8.4,"headline":"Gimp: gimp: arbitrary code execution in psd plugin due to unsigned underflow","id":"CVE-2026-59090","kev_date_added":null,"published":"2026-08-10"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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-08-11","vendors":["GIMP"]},"summary":"Local attackers can bypass macOS TCC privacy protections by using GIMP's bundled Python interpreter to access protected files without user prompts.","url":"https://insights.sbomify.com/CVE-2025-8672/"}