Quick answers
- Is CVE-2026-104073 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-104073 being exploited in the wild.
- How severe is CVE-2026-104073?
- High severity, with a CVSS score of 7.6, published 6 October 2026.
- Which products and versions are affected?
- NetBox Community NetBox 2.9.5 before 4.7.0.
- Is there a fix for CVE-2026-104073?
- Yes: fixed in 4.7.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-104073 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-104073?
- Check whether you run NetBox Community NetBox 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: 4.7.0
Technical details
The vulnerability exists in NetBox's custom link rendering, which passes the raw Django HttpRequest object to a Jinja2 template context without sanitization. An attacker with "Can add custom links" permission can embed sensitive request attributes (such as request.COOKIES['sessionid'] or API tokens) into template expressions that bypass the clean_html sanitizer and auto-exfiltrate them via image src URLs when a privileged user accesses the object. A fix was implemented in version 4.7.0 by introducing the get_safe_request_context() utility function that whitelists only safe request attributes.
Affected products
- NetBox Community NetBox 2.9.5 before 4.7.0
Timeline
- 2026-07-03: disclosed
- 2026-07-07: patched