# CVE-2026-104977: Server-side request forgery in plane

> Authenticated users can exploit incomplete SSRF protections to access internal cloud metadata and read sensitive data via link unfurling.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Oct 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-hhj8-7hv6-m74r

## What is CVE-2026-104977?

CVE-2026-104977 is a high-severity server-side request forgery vulnerability in makeplane plane, published on 5 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Plane is an open-source project management tool. Prior to 1.4.0, the fix for CVE-2026-27706 and GHSA-jcc6-f9v6-f7jw, an SSRF in work-item link unfurling shipped in v1.2.2, remains incomplete in the v1.3.1 GA release. Any authenticated project member can make the server fetch attacker-selected internal targets, including cloud metadata at 169.254.169.254, and read the response body returned as the link title or favicon. Complete hardening exists on main in PR 9163 but was not included in an earlier released tag. This issue is fixed in 1.4.0.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-104977?


## How do I fix CVE-2026-104977?

No fix has been published for CVE-2026-104977 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-104977 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-104977 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-104977 and fix it if it is affected.

What it is: CVE-2026-104977 is a high-severity server-side request forgery vulnerability in makeplane plane, published on 5 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-104977 exists.

Affected product: makeplane plane. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-104977/ (Markdown: https://insights.sbomify.com/CVE-2026-104977/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-104977
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-104977
- OSV: https://osv.dev/vulnerability/CVE-2026-104977

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-104977/
Summaries are generated and may contain mistakes; the official description above is the record.