Skip to main content
VulnerabilityPublished Updated

CVE-2024-22533: Before Beetl · Code Injection

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical : upgrade to 3.15.12 as a priority.

Data as of 26 Oct 2026, 12:29 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.0% chance of exploitation in 30 days – higher than 63% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.15.12
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Feb 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade com.ibeetl/beetl to 3.15.12.

Affected software

ProductAffectedFixed in
Mavencom.ibeetl/beetlpkg:maven/com.ibeetl/beetlOther threatsAffected
  • <3.15.12
Fixed in
  • 3.15.12

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Immediately upgrade Beetl to version 3.15.12 or later, where the vulnerability is patched.
  2. If upgrading is not immediately possible, implement strict input validation and sanitization on all template inputs to prevent injection of malicious code.
  3. Employ a whitelist-based security manager or sandboxing approach rather than relying on blacklist filtering to control template execution.
  4. Restrict network exposure of applications using Beetl to trusted internal networks or VPNs to reduce remote attack vectors.
  5. Monitor application logs and network traffic for unusual template rendering activities or error messages indicative of exploitation attempts.
  6. Conduct code reviews and penetration testing focused on template injection vulnerabilities in applications using Beetl.
  7. Apply the principle of least privilege to the application runtime environment to limit the impact of potential code execution.
  8. Stay informed about updates from Beetl maintainers and security advisories for any new patches or mitigation guidance.

Description

Before Beetl v3.15.12, the rendering template has a server-side template injection (SSTI) vulnerability. When the incoming template is controllable, it will be filtered by the DefaultNativeSecurityManager blacklist. Because blacklist filtering is not strict, the blacklist can be bypassed, leading to arbitrary code execution.

References

Community reviews

Loading reviews…