Quick answers
- Is CVE-2026-84989 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-84989 being exploited in the wild.
- How severe is CVE-2026-84989?
- High severity, with a CVSS score of 7.1, published 3 September 2026.
- Which products and versions are affected?
- Ntopng 6.7.0 through 6.7.260717.
- Is there a fix for CVE-2026-84989?
- A patch was published on 2026-07-17: Version 6.7.260718 released with fix Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-84989 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-84989?
- Check whether you run Ntopng 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.
Technical details
The vulnerability is a missing authorization check (CWE-862) in two REST API v2 endpoints: POST /lua/rest/v2/delete/tag/tag.lua and POST /lua/rest/v2/edit/tag/tag.lua. Both endpoints manage ntopng's tag/badge feature but perform no role or privilege verification before executing tag deletion or modification operations. An authenticated user with network access to the ntopng web interface can exploit these endpoints to delete or rename any tag in the system by sending a crafted POST request with a valid session and CSRF token. The underlying tag_badge_utils Lua module also lacks authorization checks and directly modifies a shared Redis hash without ownership validation. ntopng version 6.7.260718 and later contain the fix.
Affected products
- ntop ntopng 6.7.0 through 6.7.260717
Timeline
- 2026-07-17: disclosed
- 2026-07-17: patched: Version 6.7.260718 released with fix