What is CVE-2024-32979?

CVE-2024-32979 is a high-severity cross-site scripting (XSS) vulnerability in nautobot (pip), affecting versions >= 1.5.0, < 1.6.20. It is fixed in 1.6.20, 2.2.3. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

How severe is CVE-2024-32979?

CVE-2024-32979 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of nautobot are affected by CVE-2024-32979?

nautobot (pip) versions >= 1.5.0, < 1.6.20 is affected.

Is there a fix for CVE-2024-32979?

Yes. CVE-2024-32979 is fixed in 1.6.20, 2.2.3. Upgrade to this version or later.

Is CVE-2024-32979 exploitable, and should I be worried?

Whether CVE-2024-32979 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2024-32979 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2024-32979?

Upgrade: nautobot to 1.6.20 or later, nautobot to 2.2.3 or later.

CVE-2024-32979 in nautobot | Intelligent Application Security

Q: How severe is CVE-2024-32979?

CVE-2024-32979 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of nautobot are affected by CVE-2024-32979?

nautobot (pip) versions >= 1.5.0, < 1.6.20 is affected.

Q: Is there a fix for CVE-2024-32979?

Yes. CVE-2024-32979 is fixed in 1.6.20, 2.2.3. Upgrade to this version or later.

Q: Is CVE-2024-32979 exploitable, and should I be worried?

Whether CVE-2024-32979 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2024-32979 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2024-32979?

Upgrade: nautobot to 1.6.20 or later, nautobot to 2.2.3 or later.

Summary

Workarounds

No workaround has been identified

References

#5646
#5647

Credit to Michael Panorios for reporting this issue.

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.

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2024-32979 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.6.20, 2.2.3); upgrading removes the vulnerable code path.

Affected versions

nautobot (>= 1.5.0, < 1.6.20) nautobot (>= 2.0.0, < 2.2.3)

Security releases

nautobot → 1.6.20 (pip) nautobot → 2.2.3 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Fixed in Nautobot 1.6.20 and 2.2.3.

Frequently Asked Questions

What is CVE-2024-32979? CVE-2024-32979 is a high-severity cross-site scripting (XSS) vulnerability in nautobot (pip), affecting versions >= 1.5.0, < 1.6.20. It is fixed in 1.6.20, 2.2.3. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
How severe is CVE-2024-32979? CVE-2024-32979 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of nautobot are affected by CVE-2024-32979? nautobot (pip) versions >= 1.5.0, < 1.6.20 is affected.
Is there a fix for CVE-2024-32979? Yes. CVE-2024-32979 is fixed in 1.6.20, 2.2.3. Upgrade to this version or later.
Is CVE-2024-32979 exploitable, and should I be worried? Whether CVE-2024-32979 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2024-32979 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2024-32979?
- Upgrade nautobot to 1.6.20 or later
- Upgrade nautobot to 2.2.3 or later

Other vulnerabilities in nautobot

CVE-2026-44798 CVE-2026-44797 CVE-2026-44796 CVE-2026-44794 CVE-2026-34203