Quick answers
- Is CVE-2026-105628 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-105628 being exploited in the wild.
- How severe is CVE-2026-105628?
- High severity, with a CVSS score of 7.6, published 5 October 2026.
- Which products and versions are affected?
- Plane before 1.4.0.
- Is there a fix for CVE-2026-105628?
- Yes: fixed in 1.4.0. Until then: Restrict OAuth avatar fetching to explicitly whitelisted external domains or disable OAuth avatar synchronization until upgrading to version 1.4.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-105628 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-105628?
- Check whether you run Plane at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 1.4.0
Restrict OAuth avatar fetching to explicitly whitelisted external domains or disable OAuth avatar synchronization until upgrading to version 1.4.0.
Technical details
The OAuth avatar synchronization flow in Plane prior to 1.4.0 uses an unvalidated requests.get() call with default redirect-following enabled to download avatar_url values from OAuth providers. An attacker can supply a malicious avatar URL that redirects to internal-only resources (e.g., cloud metadata endpoints); the fetched response is stored as a user avatar and exposed via /api/assets/v2/static/{asset_id}/, enabling exfiltration of internal content. The fix implements IP validation, blocks internal address ranges, and validates/pins each redirect hop before following.
Affected products
- Plane Plane before 1.4.0
Timeline
- 2026-10-05: disclosed
- 2026-05-31: patched: Fix merged in pull request #9163