Skip to main content
VulnerabilityPublished Updated

CVE-2026-105636: makeplane plane · Server-Side Request Forgery (SSRF)

Affects makeplane planeSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.9 Critical : upgrade to 1.4.0 as a priority.

Data as of 19 Nov 2026, 20:25 UTC

CVSS 3.1 base score
9.9Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.4.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade plane and makeplane/plane to 1.4.0.

Affected software

ProductAffectedFixed in
makeplaneplaneAffected
  • <1.4.0
Fixed in
  • 1.4.0
GitHubmakeplane/planepkg:github/makeplane/planeOther threatsAffected
  • <1.4.0
Fixed in
  • 1.4.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

This vulnerability is fixed in Plane version 1.4.0. Users should upgrade to version 1.4.0 or later to remediate this issue. There is no indication that temporary mitigations or workarounds exist. Patch status is confirmed fixed in 1.4.0.

Description

CVE-2026-105636 is a critical Server-Side Request Forgery (SSRF) vulnerability in the open-source project management tool Plane prior to version 1.4.0. The vulnerability arises because the webhook delivery task follows HTTP redirects without validating the final redirect target URL. Although the original webhook URL is checked to block private and reserved addresses, the redirected URL is not validated. This allows an attacker who can create a workspace to register a webhook that redirects to internal addresses, enabling the Plane worker to access internal resources such as cloud metadata. The response from these internal requests is stored in webhook logs, which the attacker can then retrieve via the webhook-logs API. This issue is fixed in Plane version 1.4.0.

References

Community reviews

Loading reviews…