CVE-2026-25776
Code injection in Movable Type enables remote Perl script execution.
Is CVE-2026-25776 being exploited?
Not confirmed. CVE-2026-25776 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.47% probability of exploitation in the next 30 days.
How severe is CVE-2026-25776?
CVE-2026-25776 is rated Critical with a CVSS score of 9.3. 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-25776?
Yes. A fix has been recorded for CVE-2026-25776. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-25776 affect?
CVE-2026-25776 affects Movable Type. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-25776?
Patch/upgrade when available; monitor for signs of exploitation.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution via crafted input; attacker can run arbitrary Perl on the server and take full control.
Immediate action required
- affected9.1.0 and earlier
- affected9.0.6 and earlier
- affected8.8.2 and earlier
- affected8.0.9 and earlier
- affected5.1 to 5.18
- affected5.2
- affected5.2.1 to 5.2.13
- affected6.0
- affected6.0.1 to 6.8.8
- affected7 r.4207 to r.5510
- affected8.4.0 to 8.4.4
- affected1.0 to 1.68
- affected9.1.0 and earlier
- affected9.0.6 and earlier
- affected8.8.2 and earlier
- affected8.0.9 and earlier
- affected9.1.0 and earlier
- affected9.0.6 and earlier
- affected2.14 and earlier
- affected9.1.0 and earlier
- affected9.0.6 and earlier
- affected2.14 and earlier
- affected2.14 and earlier
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.