CVE-2026-44986
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedPenpot is an open-source design tool for design and code collaboration. Prior to 2.14.5, Penpot exposed teams_invitations.clj invitation tokens from create-team-invitations, embedded an existing profile id in auth.clj prepare-register-profile, and had auth.clj register-profile issue a session based on the invitation email match without password verification, allowing a registered user to take over any non-blocked profile. This issue is fixed in version 2.14.5.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIn Penpot versions prior to 2.14.5, the create-team-invitations endpoint in teams_invitations.clj exposed invitation tokens, and auth.clj's register-profile function issued sessions based solely on invitation email matching without requiring password verification. This allowed any registered user to take over any non-blocked profile by leveraging exposed invitation tokens.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Penpot versionCheck the Penpot application version by accessing the admin interface, checking the Docker container label, or querying the API endpoint that returns version informationAffected if The installed version is earlier than 2.14.5
-
Verify team invitation endpoint accessibilitySend a request to the create-team-invitations endpoint (typically /api/teams/:team-id/invitations) using valid authentication to see if it returns invitation tokens in the responseAffected if The endpoint returns invitation tokens in plain text to authorized users
-
Check for invitation token exposure in audit logsReview application logs for any create-team-invitations API calls and inspect whether the response body contains invitation tokens that should not be exposedAffected if Logs show invitation tokens being returned in API responses
-
Inspect session creation behaviorTest the register-profile function by creating an invitation, then attempting to register a new account using the invited email address without providing a valid passwordAffected if The system creates a session for the invited email without verifying the password against the invitation token
-
Detect unauthorized session creationMonitor authentication logs or audit trails for session creation events where the account email matches a team invitation but password verification was not performedAffected if Sessions are created for invited email addresses without proper password or token validation
You are affected if Penpot version is earlier than 2.14.5 AND the team invitation functionality is accessible, as the combination allows invitation token exposure and password-less session takeover.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Penpot to version 2.14.5 or later. As an interim measure, disable team invitation functionality if possible and monitor for unauthorized session creation.
2.14.5
- 1. Back up your Penpot database and configuration files before upgrading
- 2. Check your current Penpot version by running `penpotctl version` or checking the admin panel
- 3. Stop the Penpot service
- 4. Upgrade Penpot to version 2.14.5 using your deployment method (Docker, Kubernetes, or direct binary)
- 5. Restart the Penpot service
- 6. Verify the upgrade was successful by checking the version and logging in
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation20.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,864.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-44986 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-44986 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data