Skip to content
Applications

CVE-2026-69100

8.7
High
EPSS 0.55%Patch availableAug 5, 2026

RCE via unsandboxed Groovy templates in LAMP Rapid Development Platform.

common questions

Is CVE-2026-69100 being exploited?

Not confirmed. CVE-2026-69100 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.55% probability of exploitation in the next 30 days.

How severe is CVE-2026-69100?

CVE-2026-69100 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-69100?

Yes. A fix has been recorded for CVE-2026-69100. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-69100 affect?

CVE-2026-69100 affects LAMP Rapid Development Platform <= 5.6.2, GlueFactory component, Message template endpoints (template/script fields), Servers running embedded Groovy runtime. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-69100?

Apply commit 84b0c27/vendor patch; disable template scripting and restrict template endpoints.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
LAMP Rapid Development Platform <= 5.6.2GlueFactory componentMessage template endpoints (template/script fields)Servers running embedded Groovy runtime
impact

Remote code execution: attackers can inject Groovy scripts into template fields to execute arbitrary OS commands as the application user.

action required

Immediate action required

affected versions
dromara lamp-cloud
  • affected<= 5.6.2
vendor says fixed in84b0c27d3693e468c2c690d9fbc8ea9c22cd34e3

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free