Quick answers
- Is CVE-2026-58593 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-58593 being exploited in the wild.
- How severe is CVE-2026-58593?
- High severity, with a CVSS score of 7.5, published 1 July 2026.
- Which products and versions are affected?
- NodeBB <= 4.13.2.
- Is there a fix for CVE-2026-58593?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-58593 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-58593?
- Check whether you run NodeBB 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
NodeBB does not bind the claimed author of an inbound ActivityPub object to the authenticated remote actor. While the inbound middleware verifies the HTTP-signature and the origin of the object ID, it fails to validate that the 'attributedTo' field corresponds to the sender. In the object mock component, 'attributedTo' is used directly as a user ID (uid). Because the 'actors.assert' function ignores numeric identifiers without re-deriving the uid, a remote actor can set 'attributedTo' to a numeric value (e.g., 1 for the administrator). This results in the post or message being attributed to that local user. This vulnerability requires the ActivityPub/federation feature to be enabled.
Affected products
- NodeBB NodeBB <= 4.13.2
Timeline
- 2026-07-01: advisory: Vulnerability published by VulnCheck and NVD