How severe is CVE-2024-32979?

CVE-2024-32979 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2024-32979?

CVE-2024-32979 affects the following packages: nautobot (PyPI), nautobot (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2024-32979?

Update nautobot to 1.6.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-32979 is resolved across your whole dependency graph.

How do I detect CVE-2024-32979 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nautobot, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-32979 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2024-32979 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-32979 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2024-32979?

CVE-2024-32979 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 42th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2024-32979?

CVE-2024-32979 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2024-32979 published, and has it been updated?

CVE-2024-32979 was published on May 1, 2024 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

HIGH severity

CVE-2024-32979 — nautobot

HIGHFix: nautobot/nautobot@42440eb

CVE-2024-32979 is a high-severity (CVSS 7.5) Cross-site Scripting (XSS) vulnerability in nautobot. A fix is available for nautobot — see the affected versions and patch details below.

Reflected Cross-site Scripting potential in all object list views in Nautobot

Also known asGHSA-jxgr-gcj5-cqqgPYSEC-2026-1686

Published

May 1, 2024

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-32979.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs42th percentile — riskier than 42% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

🐍nautobot🐍nautobot

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Impact

It was discovered that due to improper handling and escaping of user-provided query parameters, a maliciously crafted Nautobot URL could potentially be used to execute a Reflected Cross-Site Scripting (Reflected XSS) attack against users. All filterable object-list views in Nautobot are vulnerable, including:

/dcim/location-types/
/dcim/locations/
/dcim/racks/
/dcim/rack-groups/
/dcim/rack-reservations/
/dcim/rack-elevations/
/tenancy/tenants/
/tenancy/tenant-groups/
/extras/tags/
/extras/statuses/
/extras/roles/
/extras/dynamic-groups/
/dcim/devices/
/dcim/platforms/
/dcim/virtual-chassis/
/dcim/device-redundancy-groups/
/dcim/interface-redundancy-groups/
/dcim/device-types/
/dcim/manufacturers/
/dcim/cables/
/dcim/console-connections/
/dcim/power-connections/
/dcim/interface-connections/
/dcim/interfaces/
/dcim/front-ports/
/dcim/rear-ports/
/dcim/console-ports/
/dcim/console-server-ports/
/dcim/power-ports/
/dcim/power-outlets/
/dcim/device-bays/
/dcim/inventory-items/
/ipam/ip-addresses/
/ipam/prefixes
/ipam/rirs/
/ipam/namespaces/
/ipam/vrfs/
/ipam/route-targets/
/ipam/vlans/
/ipam/vlan-groups/
/ipam/services/
/virtualization/virtual-machines/
/virtualization/interfaces/
/virtualization/clusters/
/virtualization/cluster-types/
/virtualization/cluster-groups/
/circuits/circuits/
/circuits/circuit-types/
/circuits/providers/
/circuits/provider-networks/
/dcim/power-feeds/
/dcim/power-panels/
/extras/secrets/
/extras/secrets-groups/
/extras/jobs/
/extras/jobs/scheduled-jobs/approval-queue/
/extras/jobs/scheduled-jobs/
/extras/job-results/
/extras/job-hooks/
/extras/job-buttons/
/extras/object-changes/
/extras/git-repositories/
/extras/graphql-queries/
/extras/relationships/
/extras/notes/
/extras/config-contexts/
/extras/config-context-schemas/
/extras/export-templates/
/extras/external-integrations/
/extras/webhooks/
/extras/computed-fields/
/extras/custom-fields/
/extras/custom-links/

as well as any similar object-list views provided by any Nautobot App.

Patches

Fixed in Nautobot 1.6.20 and 2.2.3.

Workarounds

No workaround has been identified

References

#5646
#5647

Credit to Michael Panorios for reporting this issue.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`nautobot`	≥ 1.5.0&&< 1.6.20	1.6.20`pip install --upgrade 'nautobot==1.6.20'`
🐍PyPI	`nautobot`	≥ 2.0.0&&< 2.2.3	2.2.3`pip install --upgrade 'nautobot==2.2.3'`

Affected Products

1 product · 2 configurations

Application

nautobotnetworktocode

≥ 2.0.0 && < 2.2.3

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nautobot, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update nautobot to 1.6.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-32979 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

### Impact It was discovered that due to improper handling and escaping of user-provided query parameters, a maliciously crafted Nautobot URL could potentially be used to execute a Reflected Cross-Site Scripting (Reflected XSS) attack against users. All filterable object-list views in Nautobot are vulnerable, including: - /dcim/location-types/ - /dcim/locations/ - /dcim/racks/ - /dcim/rack-groups/ - /dcim/rack-reservations/ - /dcim/rack-elevations/ - /tenancy/tenants/ - /tenancy/tenant-groups/ - /extras/tags/ - /extras/statuses/ - /extras/roles/ - /extras/dynamic-groups/ - /dcim/devices/ - /