Threat reportVulnerabilityTL-2026-0980
ServiceNow Scripted REST Resource Unauthenticated Access - /api/now/related_list_edit/create
A Scripted REST Resource endpoint (/api/now/related_list_edit/create) on ServiceNow systems was configured with unauthenticated access (requires_authentication = false). Attackers from IP 51.159.98.241 successfully accessed backend functionality and executed table queries without authentication.
Key facts
| Identifiers | TL-2026-0980 |
|---|---|
| Also known as | ServiceNow related_list_edit Unauthenticated Access, ServiceNow API Authentication Bypass |
| Severity | CRITICAL |
| Affected products | ServiceNow Now Platform |
| Weaknesses (CWE) | CWE-306, CWE-862, CWE-863 |
| MITRE ATT&CK techniques | T1016 System Network Configuration Discovery, T1030 Data Transfer Size Limits, T1048 Exfiltration Over Alternative Protocol, T1071 Application Layer Protocol, T1074 Data Staged, T1133 External Remote Services, T1190 Exploit Public-Facing Application, T1213 Data from Information Repositories, T1485 Data Destruction, T1486 Data Encrypted for Impact, T1526 Cloud Service Discovery, T1548 Abuse Elevation Control Mechanism and 3 more in the attack flow |
| Motivation | UNKNOWN |
| Target sectors | software-development, cloud-infrastructure, financial-services, health, government administration, manufacturing, telecoms |
| Target regions | EMEA, AMER, APAC |
| Detection rules | 9 (1 shown free) |
| Sources | 5 cited sources |
Detection coverage
As of 2026-06-09, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-0980 across Splunk SPL, Microsoft KQL and Sigma, covering 15 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.
Free detection: ServiceNow API Unauthenticated Access — related_list_edit/create Exploitation
Detects unauthenticated HTTP requests to the vulnerable /api/now/related_list_edit/create endpoint. Identifies exploitation of misconfigured requires_authentication = false, indicating initial access via T1190 (Exploit Public-Facing Application). Alerts on HTTP 200 responses without Authorization headers or session cookies.
- Languages: Splunk SPL, Microsoft KQL, Sigma
- ATT&CK: T1190, T1133, T1556
- Data sources: http_logs, web_proxy, web_application_firewall
- Severity: critical
- Confidence: high
Splunk SPL
index=main sourcetype=http_log uri="/api/now/related_list_edit/create*" status=200 | search NOT (http_authorization=* OR http_cookie=*JSESSIONID*) | stats count as request_count, values(user_agent) as user_agents, values(src_ip) as source_ips by uri, dest, host | where request_count >= 1 OR like(user_agents, "%curl%") OR like(user_agents, "%wget%") OR like(user_agents, "%python%")Microsoft KQL
DeviceNetworkEvents | where RemoteUrl contains "/api/now/related_list_edit/create" | where HttpStatusCode == 200 | where isempty(AuthenticationHeader) or AuthenticationHeader == "" | where isempty(HttpCookie) or HttpCookie == "" | where UserAgent contains "curl" or UserAgent contains "wget" or UserAgent contains "python-requests" | summarize RequestCount=count(), TableParams=make_set(RequestQuery) by DeviceId, RemoteIp, UserAgent | where RequestCount >= 1Sigma
title: ServiceNow API Unauthenticated Access - Exploitation Phase
id: 3f886f2a-0001-0001-0001-000000000001
status: experimental
description: Detects unauthenticated HTTP requests to /api/now/related_list_edit/create endpoint indicating exploitation of misconfigured requires_authentication parameter (CVE-level configuration flaw)
references:
- https://threats.wiz.io/all-incidents/servicenow-unauthenticated-access-incident
author: Threadlinqs Team
date: 2026-06-28
tags:
- attack.initial_access
- attack.t1190
- attack.t1133
- attack.defense_evasion
- attack.t1556
logsource:
product: web
category: web_application_firewall
detection:
selection_endpoint:
uri|endswith: '/api/now/related_list_edit/create'
http_method: 'GET|POST|PUT|DELETE'
selection_no_auth:
http_authorization: null
http_status_code: '200'
filter_user_agent:
user_agent|contains:
- 'curl'
- 'wget'
- 'python-requests'
condition: selection_endpoint and selection_no_auth and filter_user_agent
falsepositives:
- Legitimate automation tools making unauthenticated requests (rare in ServiceNow production)
- Internal monitoring scripts without proper auth headers (configure service accounts)
level: criticalKnown false positives:
- Internal monitoring tools without proper authentication; Legitimate API automation scripts misconfigured without auth headers
Tuning notes: Whitelist known internal API automation tools by IP/user-agent. Adjust request_count threshold based on environment baseline. Monitor for brute-force patterns by adding rate-based alerting (>5 requests/minute from single source IP). Exclude internal monitoring infrastructure from detection scope.
- ServiceNow API Unauthenticated Access — related_list_edit/create Exploitation · unlock with TL Creds
- ServiceNow Guest User Abusing Table Query API — Post-Exploitation Data Access · unlock with TL Creds
- ServiceNow API Large Data Transfer via Guest Session — Exfiltration Detection · unlock with TL Creds
- ServiceNow API Unauthenticated Access — related_list_edit/create Exploitation · unlock with TL Creds
- ServiceNow Guest User Abusing Table Query API — Post-Exploitation Data Access · unlock with TL Creds
- ServiceNow API Large Data Transfer via Guest Session — Exfiltration Detection · unlock with TL Creds
- ServiceNow Guest User Abusing Table Query API — Post-Exploitation Data Access · unlock with TL Creds
- ServiceNow API Large Data Transfer via Guest Session — Exfiltration Detection · unlock with TL Creds
Indicators of compromise
As of 2026-06-09, Threadlinqs Intelligence tracks 15 indicators of compromise for TL-2026-0980.
Sample indicators (1 of 15)
- IP address:
51.159.98[.]241
Defanged, TLP:CLEAR. Full set of 15 indicators: unlock with TL Creds.
Technical analysis
A critical misconfiguration in ServiceNow Scripted REST Resources allowed unauthenticated access to the /api/now/related_list_edit/create endpoint. The endpoint was configured with requires_authentication set to false, bypassing standard authentication and authorization controls. Security researchers and affected customers observed multiple successful access attempts originating from IP address 51.159.98.241 (OVH SA infrastructure, France). The attacker was able to execute backend queries and access related list data without providing valid credentials. Affected systems included customer instances running the Australia release and those with certain pre-release configuration changes. Because requests were processed without an authenticated user context, activity was logged under the Guest user account, complicating forensic analysis and attribution. ServiceNow indicated that successful table queries were observed in a subset of customer environments, suggesting potential data exfiltration. The vulnerability appears to stem from improper configuration of Scripted REST API endpoints rather than a traditional code vulnerability, though it represents a serious authentication bypass. Multiple customers were notified directly by ServiceNow regarding the scope of exposure.
MITRE ATT&CK techniques by tactic:
Discovery
T1016 System Network Configuration Discovery; T1526 Cloud Service Discovery
Exfiltration
T1030 Data Transfer Size Limits; T1048 Exfiltration Over Alternative Protocol
Command and Control
T1071 Application Layer Protocol
Collection
T1074 Data Staged; T1213 Data from Information Repositories
Initial Access
T1133 External Remote Services; T1190 Exploit Public-Facing Application
Impact
T1485 Data Destruction; T1486 Data Encrypted for Impact
Privilege Escalation
T1548 Abuse Elevation Control Mechanism
Lateral Movement
T1550 Use Alternate Authentication Material
defense-impairment
T1556 Modify Authentication Process
defense-evasion
Remediation
Patches
- Apply ServiceNow security patches for authentication validation
- Update Scripted REST Resource configurations to enforce requires_authentication = true
- Implement API access controls via ACLs on related_list_edit and similar endpoints
Immediate actions
- Audit all Scripted REST Resource endpoints for requires_authentication = false configuration
- Review API access logs for requests from IP 51.159.98.241 and similar external IPs
- Check Guest user account activity logs for suspicious table queries
- Block IP 51.159.98.241 and OVH IP ranges 51.159.0.0/16 at perimeter if not required
- Enable request logging and monitoring on all REST API endpoints
Workarounds
- Disable the /api/now/related_list_edit/create endpoint if not required
- Restrict endpoint access via network firewall rules to known internal sources only
- Implement reverse proxy authentication layer in front of ServiceNow
Longer-term hardening
- Implement API gateway with authentication enforcement before ServiceNow instance
- Deploy EDR with behavioral detection for suspicious database queries
- Enforce API authentication requirements via policy in development/configuration controls
- Implement network segmentation to restrict API access to known sources
- Deploy UEBA to detect anomalous guest account activity
- Implement query activity monitoring on backend tables
- Review and audit all Scripted REST Resources and custom API endpoints
Affected and fixed versions
- ServiceNow — Now Platform
Vulnerable versions: Australia release; Pre-release versions with configuration changes
Timeline
- ServiceNow confirms observing successful table queries in subset of customer environments; notifies affected customers directly
- Multiple instances of successful access attempts from IP locked-ioc-2 confirmed by security researchers and affected customers
- Security researchers publicly disclose /api/now/related_list_edit/create endpoint misconfiguration allowing unauthenticated access
- Wiz Threat Intelligence publishes detailed analysis of ServiceNow unauthenticated access incident affecting Australia release and pre-release environments
- Security researchers on Twitter/X begin analyzing incident scope and implications for ServiceNow customer base
- Reddit r/servicenow community discusses incident; multiple customers report similar unauthenticated access attempts in their logs
- Forensic analysis reveals requests logged under Guest user account, complicating attribution and forensic timeline reconstruction
- ServiceNow provides guidance to customers on auditing Scripted REST Resource configurations and enforcing requires_authentication parameter
Sources cited
- OWASP - Broken Authentication (A07:2021) owasp.org · Advisory · 2021-09-24
- ServiceNow Scripted REST Resources Documentation docs.servicenow.com · Vendor report · 2024-01-01
- Reddit r/servicenow - Community Discussion of Incident reddit.com · News · 2026-06-10
- Twitter Security Researcher Coverage x.com · News · 2026-06-09
- Wiz Threat Intelligence - ServiceNow Unauthenticated Access Incident Wiz · 2026-06-09
Previous and next in vulnerability
Drafted by the Threadlinqs research pipeline from 5 sources; published ; last updated —.