dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-45806

HIGH · 7.7 CVSS v3.1 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/100
Remediation priority · High
Remotely reachable Zero-click 5 weeks old

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 · unedited
Penpot is an open-source design tool for design and code collaboration. Prior to 2.15.0, Penpot's remote image import passed the user-controlled url from frontend/src/app/main/data/workspace/media.cljs into the backend RPC method :create-file-media-object-from-url in backend/src/app/rpc/commands/media.clj, where media/download-image in backend/src/app/media.clj used the shared HTTP client without destination filtering, allowing an authenticated file editor to reach internal-only endpoints. This issue is fixed in version 2.15.0.

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 confidence

This is a Server-Side Request Forgery (SSRF) vulnerability in Penpot's remote image import feature. The application accepts a user-controlled URL from the frontend and passes it to the backend's media download function without proper destination filtering, allowing authenticated file editors to make the server request to arbitrary URLs including internal-only network endpoints.

MitigationUpgrade to Penpot version 2.15.0 or later which implements proper URL destination filtering. If immediate upgrading is not possible, restrict network access to the Penpot server to prevent SSRF attacks against internal services.

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Penpot installation
    Locate the Penpot application on your system or confirm it is running as a service. Check for penpot process, container, or installation directory.
    Affected if Penpot server is present in the environment
  2. Determine installed Penpot version
    Check the running Penpot version via the admin interface, container image tag, package version, or by querying the application's API endpoint for version information.
    Affected if Version is prior to 2.15.0 (the fixed release)
  3. Verify remote image import feature exists
    Log in as an authenticated user with file editor permissions. Navigate to the image import functionality and confirm the remote URL import option is available in the UI.
    Affected if Remote image import feature is accessible to authenticated editors
  4. Check network access configuration
    Inspect Penpot's network configuration or firewall rules to determine if the server has unrestricted outbound network access.
    Affected if Server can make outbound HTTP/HTTPS requests to arbitrary destinations
  5. Confirm internal network exposure
    Review whether the Penpot server can reach internal-only network endpoints (e.g., internal services, localhost, private IP ranges) from its network position.
    Affected if Server has access to internal network resources that should not be externally reachable

You are affected if running a Penpot version below 2.15.0 with the remote image import feature accessible to authenticated editors and the server has network access to internal resources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Penpot version 2.15.0 or later which implements proper URL destination filtering. If immediate upgrading is not possible, restrict network access to the Penpot server to prevent SSRF attacks against internal services.

Recommended fix High confidence

2.15.0

  1. Backup the existing Penpot data and configuration
  2. Stop the Penpot service
  3. Update Penpot to version 2.15.0 using the appropriate installation method (Docker, source, or package manager)
  4. Verify the configuration files are compatible with version 2.15.0
  5. Start the Penpot service
  6. Confirm the service is running and the remote image import feature works correctly

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45806 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45806 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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