{"answers":{"affected":"2 open source packages ship an affected version, including io.pebbletemplates:pebble. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-1686 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2025-1686 is a medium-severity path traversal vulnerability in io.pebbletemplates:pebble, published on 27 Feb 2025. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-1686 and fix it if it is affected.\n\nWhat it is: CVE-2025-1686 is a medium-severity path traversal vulnerability in io.pebbletemplates:pebble, published on 27 Feb 2025. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-1686 exists.\n\nAffected packages and fixed versions:\n- io.pebbletemplates:pebble (Maven): affected all versions up to 3.2.3; no fix listed\n- io.pebbletemplates:pebble (Maven): affected all versions up to 3.2.3; no fix listed\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-1686/ (Markdown: https://insights.sbomify.com/CVE-2025-1686/index.md)","id":"CVE-2025-1686","markdown":"https://insights.sbomify.com/CVE-2025-1686/index.md","name":"CVE-2025-1686","record":{"aliases":["GHSA-p75g-cxfj-7wrx","ROOT-APP-MAVEN-CVE-2025-1686"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Java template engine","requires_auth":"high_privilege","summary":"A high-privileged attacker can read sensitive local files via malicious templates using the include tag in the Pebble template engine.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[{"product":"pebble_templates","vendor":"pebbletemplates"}],"cvss":{"score":6.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-73","name":"External Control of File Name or Path"}],"description":"Versions of the package io.pebbletemplates:pebble from 0 and before 4.1.0 are vulnerable to External Control of File Name or Path via the include tag. A high privileged attacker can access sensitive local files by crafting malicious notification templates that leverage this tag to include files like /etc/passwd or /proc/1/environ.\r\r Workaround\r\rThis vulnerability can be mitigated by disabling the include macro in Pebble Templates:\r\rjava\rnew PebbleEngine.Builder()\r            .registerExtensionCustomizer(new DisallowExtensionCustomizerBuilder()\r                    .disallowedTokenParserTags(List.of(\"include\"))\r                    .build())\r            .build();","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Pebble has Arbitrary Local File Inclusion (LFI) Vulnerability via `include` macro","id":"CVE-2025-1686","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"path_traversal","year":"2025"},"n_packages":2,"n_references":5,"next":{"headline":"Cardealer \u003c= 1.6.4 - Cross-Site Request Forgery to User Update via update_user_profile","id":"CVE-2025-1687"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["3.2.3"],"package":"io.pebbletemplates:pebble","purl":null,"source":"GHSA-p75g-cxfj-7wrx"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["3.2.3"],"package":"io.pebbletemplates:pebble","purl":"pkg:maven/io.pebbletemplates/pebble","source":"GHSA-p75g-cxfj-7wrx"}],"prev":{"headline":"Symbolic Link Exploit in 1E Client's - Nomad module allows Arbitrary File Deletion","id":"CVE-2025-1683"},"products":["io.pebbletemplates:pebble"],"published":"2025-02-27","related":[{"cvss_score":9.8,"headline":"Pebble Templates protection mechanism bypass can lead to arbitrary code execution","id":"CVE-2022-37767","kev_date_added":null,"published":"2022-09-12"},{"cvss_score":9.8,"headline":"Pebble Templates Improper Input Validation vulnerability","id":"CVE-2019-19899","kev_date_added":null,"published":"2019-12-18"}],"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":"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-19","vendors":["n/a"]},"summary":"A high-privileged attacker can read sensitive local files via malicious templates using the include tag in the Pebble template engine.","url":"https://insights.sbomify.com/CVE-2025-1686/"}