Nautobot Single Source of Truth (SSoT) has an unauthenticated ServiceNow configuration URL

Exploitation

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

CVSS

5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2025-62607: 0.29% estimated exploitation activity in the next 30 days; percentile 22.15 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

The servicenow config URL is using a generic django View with no authentication. URL: /plugins/ssot/servicenow/config/ Impact What kind of vulnerability is it? Who is impacted? An Unauthenticated attacker could access this page to view the Service Now public instance name e.g. companyname.service-now.com. This is considered low-value information. This does not expose the Secret, the Secret Name, or the Secret Value for the Username/Password for Service-Now.com. An unauthenticated member would not be able to change the instance name, nor set a Secret. There is not a way to gain access to other pages Nautobot through the unauthenticated Configuration page. Patches Has the problem been patched? What versions should users upgrade to? We highly recommend upgrading to SSoT v3.10.0 which includes this patch. Workarounds Is there a way for users to fix or remediate the vulnerability without upgrading? Disable the servicenow SSoT integration

Published by the source

21 Oct 2025, 21:46 UTC

Last modified by the source

7 Jul 2026, 17:57 UTC

Source last checked

26 Oct 2026, 13:35 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-535g-62r7-cx6v

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-535g-62r7-cx6v

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

# Patch Next advisory brief: CVE-2025-62607

Advisory: Nautobot Single Source of Truth (SSoT) has an unauthenticated ServiceNow configuration URL
IDs: CVE-2025-62607, GHSA-535g-62r7-cx6v
Record: https://patchnext.com/advisories/cve-2025-62607 (revision 2, source checked 26 Oct 2026, 13:35 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: nautobot-ssot 3.10.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI nautobot-ssot: affected < 3.10.0; fixed in 3.10.0

## Suggested inspection (read-only)
- `python -m pip show nautobot-ssot`: 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 nautobot-ssot.
- 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-535g-62r7-cx6v (OSV record GHSA-535g-62r7-cx6v lists affected ranges: PyPI nautobot-ssot >=0 <3.10.0 (fixed))
- Verified: https://github.com/advisories/GHSA-535g-62r7-cx6v (GitHub-reviewed advisory GHSA-535g-62r7-cx6v lists affected ranges: PyPI nautobot-ssot >=0 <3.10.0)

Commands are suggestions: review each one before running it.