CVE-2022-46886
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThere exists an open redirect within the response list update functionality of ServiceNow. This allows attackers to redirect users to arbitrary domains when clicking on a URL within a service-now domain.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is an open redirect vulnerability in ServiceNow's response list update functionality. Attackers can craft malicious URLs within the ServiceNow domain that redirect users to arbitrary external websites. This enables phishing attacks where users believe they are clicking a legitimate ServiceNow link but are actually being redirected to a malicious site.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= quebec= rome= san_diego= tokyoCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify your ServiceNow versionCheck the ServiceNow instance login page footer or navigate to System Diagnostics > System Information to view the exact version release (e.g., Quebec, Rome, San Diego, Tokyo)Affected if The installed version matches Quebec, Rome, San Diego, or Tokyo exactly as listed in the affected versions
-
Verify access to response list update functionalityNavigate to the response list update module in your ServiceNow instance. This is typically found in Service Catalog or Incident Management sections where response lists are configured and modifiedAffected if The response list update functionality is accessible and functional in your instance
-
Test for open redirect behaviorIf you have access, attempt to create or modify a response list entry with a redirect URL parameter (e.g., a URL pointing to an external domain) and observe if ServiceNow allows the redirect without validation or warningAffected if ServiceNow permits redirect URLs to external domains within response list entries without proper validation or sanitization
-
Review URL patterns in your instanceCheck any custom scripts, UI actions, or workflows that handle redirect functionality within the response list module. Look for URL parameters that accept external destinations without validationAffected if Custom configurations or scripts exist that accept arbitrary redirect URLs without validation
Your environment is affected if you are running ServiceNow Quebec, Rome, San Diego, or Tokyo AND the response list update functionality is accessible and allows external redirect URLs without validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedApply ServiceNow security patches as they become available. In the interim, implement URL filtering and user awareness training to mitigate phishing risks from redirect-based attacks.
Upgrade to the latest available patch/version within your current release family (e.g., latest Quebec patch, Rome patch, etc.) or migrate to a newer ServiceNow release that includes the security fix
- 1. Identify your current ServiceNow release version (Quebec, Rome, San Diego, or Tokyo) by navigating to System Properties > Instance or checking the login page footer.
- 2. Access the ServiceNow Knowledge Base at support.servicenow.com and search for CVE-2022-46886 or the related hot fix (HI) patch.
- 3. Apply the relevant security patch for your specific release version, or schedule an upgrade to a newer patch version that includes the fix.
- 4. After applying the patch, verify the fix by testing the response list update functionality to ensure redirects are properly validated.
- 5. Clear browser cache and test with a clean browser session to confirm the redirect vulnerability is remediated.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46886 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-46886 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data