netbox-data-flows has stored XSS in ObjectAlias names rendered inside DataFlow tables

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.7 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary An authenticated user who can create or edit ObjectAlias objects can store arbitrary HTML/JavaScript in an alias name. That payload is later rendered unescaped in DataFlow table views, causing a stored XSS when another user views the affected page. Details The issue is caused by unsafe HTML generation in the plugin’s custom table column renderer. Relevant code on main (bf96eac, same commit as origin/main at the time of review): - netboxdataflows/models/objectaliases.py - ObjectAlias.name is user-controlled (CharField) - ObjectAlias.str() returns self.name directly - netboxdataflows/tables/dataflows.py - DataFlowTable.sources and DataFlowTable.destinations use ObjectAliasListColumn - netboxdataflows/tables/columns.py - ObjectAliasListColumn.render() calls objectlisttostring(value.all(), linkify=True) - netboxdataflows/utils/helpers.py - objectlisttostring() builds raw anchor tags with: The alias text ({o}) is inserted into HTML without escaping, then the whole string is marked…

Published by the source

7 May 2026, 22:31 UTC

Last modified by the source

7 May 2026, 22:48 UTC

Source last checked

26 Oct 2026, 13:41 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-v7qw-hx66-4w9x

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-v7qw-hx66-4w9x

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-v7qw-hx66-4w9x

Advisory: netbox-data-flows has stored XSS in ObjectAlias names rendered inside DataFlow tables
IDs: GHSA-v7qw-hx66-4w9x
Record: https://patchnext.com/advisories/ghsa-v7qw-hx66-4w9x (revision 2, source checked 26 Oct 2026, 13:41 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: netbox-data-flows 1.5.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI netbox-data-flows: affected <= 1.5.0; fixed in 1.5.1

## Suggested inspection (read-only)
- `python -m pip show netbox-data-flows`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on netbox-data-flows.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-v7qw-hx66-4w9x (OSV record GHSA-v7qw-hx66-4w9x lists affected ranges: PyPI netbox-data-flows >=0 <1.5.1 (fixed))
- Verified: https://github.com/advisories/GHSA-v7qw-hx66-4w9x (GitHub-reviewed advisory GHSA-v7qw-hx66-4w9x lists affected ranges: PyPI netbox-data-flows >=0 <=1.5.0)

Commands are suggestions: review each one before running it.