UpTrajectory Review

ServiceNow API Vulnerability: What Small Businesses Need to Know

unlocked filing cabinet in empty office
Photo: Mikhail Nilov / Pexels

UpTrajectory Review

ServiceNow has begun notifying customers about an unauthenticated API flaw that could have let anyone pull data from affected instances. The company says it closed the hole after a bug bounty report in April, pushed a security update (KB3067321) to hosted tenants on June 5, and issued guidance (KB3067372) for self-hosted shops. Customers started talking publicly after receiving security notices and seeing reports of odd activity tied to their environments. The details are thin in the official advisory, but Reddit users point to the /api/now/related_list_edit/create endpoint, which shipped with requires_authentication set to false under specific conditions.

If your business runs on ServiceNow, this one stings. The platform often holds IT tickets, employee records, and internal security data, so an open door means more than a leaked email address. AppOmni CISO Cory Michal told CSO Online that anyone who knew the endpoint URL and how to structure the request could grab data without logging in. For a small shop, that translates to exposed help-desk queues, HR details, and incident notes that competitors or attackers could mine for leverage. Even if you self-host, you still had to apply the guidance yourself, and many operators lack the staff to patch quickly.

What stands out is the lag between discovery and disclosure. ServiceNow learned of the flaw in April, yet public discussion only erupted after customers received notifications and noticed suspicious activity. The company says that activity traces to security researchers probing the vulnerability, not to criminals, but that claim deserves scrutiny. A two-month silent remediation window leaves tenants exposed while they remain unaware. We also note the advisory's lack of technical detail: relying on Reddit threads to learn which endpoint failed is not a good look for a vendor that sells trust as a service.

The downstream effects split along hosting lines. Cloud customers got the fix automatically on June 5, but self-hosted operators had to act on KB3067372, and many small IT teams likely missed it amid daily fires. If your instance held customer data, you now face breach-notification duties and reputational risk, even if the exposure came from ServiceNow's code. Insurance carriers and auditors will ask whether you applied the patch promptly. Meanwhile, researchers scanning for vulnerable tenants may have generated logs that now complicate your own threat-hunting efforts.

Check your ServiceNow version and confirm you received KB3067321 or applied KB3067372. Review access logs for hits to the related_list_edit endpoint and flag any unauthenticated requests. If you store personal data in ServiceNow, consult counsel on notification obligations. Finally, press your vendor for clearer timelines: a 60-day gap between bug bounty report and customer notice is too long for a platform that anchors your operations.

“In practical terms, anyone who knew the endpoint URL and how to structure the request could access data from the affected ServiceNow tenant without authenticating first” — CSO Online

Takeaway: Verify your ServiceNow instance received KB3067321 or KB3067372, then audit logs for unauthenticated API access before regulators or insurers ask.

Excerpt from the original — CSO Online

ServiceNow is notifying customers after discovering and remediating a vulnerability that could have exposed data via an unauthenticated API endpoint on affected instances.

The issue emerged publicly after customers began discussing security notifications from ServiceNow and reports of suspicious activity linked to their environments.

According to the company’s advisory, the vulnerability was initially reported through ServiceNow’s bug bounty program in April, prompting an investigation and subsequent security updates. ServiceNow said hosted customers received a security update (KB3067321)  on June 5, while guidance (KB3067372) was issued for self-hosted deployments.

The flaw appears to have affected tenants running specific versions and configurations. Cory Michal, CISO at SaaS and AI security company AppOmni, said the issue involved “An unauthenticated, internet-facing …