Summary
The servicenow config URL is using a generic django View with no authentication.
URL: /plugins/ssot/servicenow/config/
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
Disable the servicenow SSoT integration
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.
A critical operation is accessible without requiring any authentication. Typical impact: any user can invoke the privileged function.
CVE-2025-62607 has a CVSS score of 5.3 (Medium). The vector is network-reachable, no privileges required, and no user interaction. 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 (3.10.0); upgrading removes the vulnerable code path.
Affected versions
Security releases
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.
Remediation advice
Has the problem been patched? What versions should users upgrade to?
We highly recommend upgrading to SSoT v3.10.0 which includes this patch.
Frequently Asked Questions
- What is CVE-2025-62607? CVE-2025-62607 is a medium-severity missing authentication for critical function vulnerability in nautobot-ssot (pip), affecting versions < 3.10.0. It is fixed in 3.10.0. A critical operation is accessible without requiring any authentication.
- How severe is CVE-2025-62607? CVE-2025-62607 has a CVSS score of 5.3 (Medium). 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-ssot are affected by CVE-2025-62607? nautobot-ssot (pip) versions < 3.10.0 is affected.
- Is there a fix for CVE-2025-62607? Yes. CVE-2025-62607 is fixed in 3.10.0. Upgrade to this version or later.
- Is CVE-2025-62607 exploitable, and should I be worried? Whether CVE-2025-62607 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-2025-62607 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-2025-62607? Upgrade
nautobot-ssotto 3.10.0 or later.