CVE-2025-62607Medium· 5.3▾ SunlitNautobot Single Source of Truth (SSoT) has an unauthenticated ServiceNow configuration URL
▾ Sunlit zone — Low / medium · no exploitation signal
impact 29.2 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Jul 8.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
0.3%
0.3% → 0.3%
The servicenow config URL is using a generic django View with no authentication.
URL: /plugins/ssot/servicenow/config/
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.
Has the problem been patched? What versions should users upgrade to? We highly recommend upgrading to SSoT v3.10.0 which includes this patch.
Is there a way for users to fix or remediate the vulnerability without upgrading? Disable the servicenow SSoT integration
nautobot-ssot < 3.10.0Upgrade to a patched release:
nautobot-ssot 3.10.0