Skip to content

← Actionable
High, CVSS 7.0

Pebble has Arbitrary Local File Inclusion (LFI) Vulnerability via include macro

CVE-2025-1686GHSA-p75g-cxfj-7wrx

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • Maven io.pebbletemplates:pebble

    Affected
    <= 3.2.3
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
7.0 · CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:H/SC:L/SI:N/SA:N · score source
EPSS
  • CVE-2025-1686: 0.85% estimated exploitation activity in the next 30 days; percentile 58.13 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary If untrusted user input is used to dynamically create a PebbleTemplate with the method PebbleEngine#getLiteralTemplate, then an attacker can include arbitrary local files from the file system into the generated template, leaking potentially sensitive information into the output of PebbleTemplate#evaluate. This is done via the include macro. Details The include macro calls PebbleTempateImpl#resolveRelativePath with the relativePath argument passed within the template: Example template: When resolveRelativePath is called, the relativePath is resolved against the PebbleTemplateImpl.name variable. https://github.com/PebbleTemplates/pebble/blob/82ad7fcf9e9eaa45ee82ae3335a1409d19c10263/pebble/src/main/java/io/pebbletemplates/pebble/template/PebbleTemplateImpl.java#L380 Unfortunately, when the template is created from a string, as is the case when PebbleEngine#getLiteralTemplate is used, the PebbleTemplateImpl.name variable is actually the entirety of the contents of the template,…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-p75g-cxfj-7wrx

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-1686

Advisory: Pebble has Arbitrary Local File Inclusion (LFI) Vulnerability via `include` macro
IDs: CVE-2025-1686, GHSA-p75g-cxfj-7wrx
Record: https://patchnext.com/advisories/cve-2025-1686 (revision 1, source checked 26 Oct 2026, 16:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven io.pebbletemplates:pebble: affected <= 3.2.3

## Suggested inspection (read-only)
- Maven io.pebbletemplates:pebble: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on io.pebbletemplates:pebble.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-p75g-cxfj-7wrx (GitHub-reviewed advisory GHSA-p75g-cxfj-7wrx lists affected ranges: Maven io.pebbletemplates:pebble >=0 <=3.2.3)

Commands are suggestions: review each one before running it.

Loading voting…