Quick answers
- Is CVE-2026-104973 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-104973 being exploited in the wild.
- How severe is CVE-2026-104973?
- High severity, with a CVSS score of 7.6, published 5 October 2026.
- Which products and versions are affected?
- Makeplane Plane before 1.4.0.
- Is there a fix for CVE-2026-104973?
- Yes: fixed in 1.4.0. Until then: Upgrade to version 1.4.0 or later, which implements a pinned-IP HTTP client that resolves and validates DNS once before connecting, eliminating the DNS rebinding window. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-104973 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-104973?
- Check whether you run Makeplane 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
Upgrade to version 1.4.0 or later, which implements a pinned-IP HTTP client that resolves and validates DNS once before connecting, eliminating the DNS rebinding window.
Technical details
The vulnerability is a DNS rebinding time-of-check-time-of-use (TOCTOU) flaw in webhook delivery. IP validation occurred when the webhook was created in the serializer, but the delivery task in webhook_task.py performed a separate DNS resolution at send time without validating the resolved IP, allowing an attacker to return different IPs for the same hostname between validation and delivery. This is fixed by using a pinned-IP HTTP client that resolves DNS once, validates the result, and connects to the validated IP literal.
Affected products
- makeplane Plane before 1.4.0
Timeline
- 2026-10-05: disclosed
- 2026-05-31: patched: Fix merged in PR #9163