dbcve.org
PlaneApplication

CVE-2026-27706

HIGH · 7.7 CVSS v3.1 Published 2026-02-25
Fix available
A fix is available. Upgrade to 1.2.2 or later.
See remediation →
83/100
Remediation priority · High
Remotely reachable Zero-click

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
Plane is an an open-source project management tool. Prior to version 1.2.2, a Full Read Server-Side Request Forgery (SSRF) vulnerability has been identified in the "Add Link" feature. This flaw allows an authenticated attacker with general user privileges to send arbitrary GET requests to the internal network and exfiltrate the full response body. By exploiting this vulnerability, an attacker can steal sensitive data from internal services and cloud metadata endpoints. Version 1.2.2 fixes the issue.

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

Full Read SSRF vulnerability in Plane's 'Add Link' feature (versions prior to 1.2.2) allows any authenticated user to send arbitrary GET requests to internal network resources and exfiltrate the complete response body, enabling access to sensitive internal services and cloud metadata endpoints.

MitigationUpgrade to Plane version 1.2.2 or later which contains the fix. Additionally, implement network segmentation and restrict access to internal services and cloud metadata endpoints as a defense-in-depth measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PlaneApplication
Affected:< 1.2.2

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. Check installed Plane version
    Access the Plane admin panel or check the package.json/Docker image tag to identify the current version number
    Affected if Version is earlier than 1.2.2 (e.g., 1.2.1, 1.2.0, 1.1.x, etc.)
  2. Verify Add Link feature availability
    Log in as an authenticated (non-admin) user and navigate to a project where links can be added. Check if the 'Add Link' feature is present and accessible.
    Affected if The Add Link feature is visible and usable by authenticated users in your environment
  3. Confirm network accessibility to internal services
    Review server network configuration to determine if the Plane host can reach internal network ranges (127.0.0.0/8, 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16) or cloud metadata endpoints (169.254.169.254)
    Affected if The Plane server has outbound HTTP access to internal network ranges or cloud metadata services
  4. Check for existing SSRF mitigations
    Inspect Plane's web application firewall (WAF) rules, proxy configurations, or network policies that may block or filter outbound requests from the application
    Affected if No SSRF protections are in place at the network or application layer

You are affected if your Plane version is earlier than 1.2.2 and the Add Link feature is accessible to authenticated users on your instance.

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
Upgrade available Upgrade to 1.2.2 or later
Fixed in 1.2.2
Interim mitigation

Upgrade to Plane version 1.2.2 or later which contains the fix. Additionally, implement network segmentation and restrict access to internal services and cloud metadata endpoints as a defense-in-depth measure.

Recommended fix High confidence

Plane version 1.2.2

  1. 1. Back up your current Plane installation and database before proceeding with the upgrade.
  2. 2. Identify your current Plane deployment method (Docker, Kubernetes, or direct installation).
  3. 3. If using Docker, update your container image to version 1.2.2 or later: docker pull plane/backend:1.2.2
  4. 4. If using Kubernetes, update your Helm chart or deployment manifest to specify version 1.2.2.
  5. 5. If using direct installation, download Plane version 1.2.2 from the official repository and follow the upgrade instructions.
  6. 6. After upgrading, verify the "Add Link" feature works correctly and that SSRF protections are in place.
  7. 7. Test that the application cannot make requests to internal network addresses (127.0.0.1, 169.254.169.254, etc.) through the Add Link feature.

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

Fix this in Plane Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27706 — 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-27706 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