Skip to content
Applications

CVE-2026-44986

9.9
Critical
EPSS 0.52%Patch availableJul 16, 2026

Auth/token flaws in Penpot allow account takeover of non-blocked profiles.

common questions

Is CVE-2026-44986 being exploited?

Not confirmed. CVE-2026-44986 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.52% probability of exploitation in the next 30 days.

How severe is CVE-2026-44986?

CVE-2026-44986 is rated Critical with a CVSS score of 9.9. 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-44986?

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

What does CVE-2026-44986 affect?

CVE-2026-44986 affects Penpot < 2.14.5, Self-hosted Penpot instances, Unpatched Penpot cloud deployments. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-44986?

Upgrade to Penpot 2.14.5; revoke pending invitations; invalidate sessions; audit accounts.

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

executive summary
technical analysis
affected
Penpot < 2.14.5Self-hosted Penpot instancesUnpatched Penpot cloud deployments
impact

Account takeover: registered users can assume other non-blocked profiles via leaked invitation tokens and auth flow issuing sessions without password verification.

action required

Immediate action required

affected versions
penpot penpot
  • affected< 2.14.5

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