SOCLYDE logo
Current languageEN
Cybersecurity newsVulnerabilityServiceNowAI

ServiceNow AI Platform: five vulnerabilities fixed

ServiceNow fixed five AI Platform CVEs. Check Australia, Yokohama and Zurich patch levels and verify the update applied to your instance.

Published on · Updated on

By Soclyde Team

Two administrators review a configuration change in a company office

In summary

  • KB3159623 covers five CVEs, including two critical flaws: CVE-2026-13016 (SQL injection) and CVE-2026-86860 (missing authorization).
  • Fixed thresholds differ across Australia, Yokohama and Zurich; four of the five flaws require no authentication.
  • MS-ISAC reported no known in-the-wild exploitation as of September 25, 2026; self-hosted customers should verify their fix.

Explore next

Soclyde resources

Article contents

On September 24, 2026, ServiceNow published KB3159623 for five AI Platform vulnerabilities: two critical and three high-severity. CVE-2026-13016 is a SQL injection; CVE-2026-86860 is a missing-authorization flaw that may allow privilege escalation. The other three involve authorization bypass or data control.

Canada’s Cyber Centre relayed the advisory on September 25. ServiceNow says hosted instances were remediated; partners and customers operating their own environments must confirm their patch level and upgrade path.

The five vulnerabilities

The batch includes CVE-2026-13016, a SQL injection issue, CVE-2026-86860, a missing-authorization issue, and CVE-2026-86857, CVE-2026-86858 and CVE-2026-86859 involving access to or manipulation of data. Consult the vendor advisory for exact vectors and fixed releases.

These descriptions express potential capabilities; they do not prove that a particular instance was accessed or changed. That distinction matters when deciding how to investigate and respond.

Compare the release families

Fixed levels differ by release family: Australia Patch 2 Hot Fix 4b W32, Patch 4 Hot Fix 3 or Patch 5; Yokohama Patch 13 Hot Fix 5a; Zurich Patch 10 Hot Fix 3b, Patch 10 Hot Fix 4a W32 or Patch 11 Hot Fix 3. Compare your level against the complete official list because some branches have multiple upgrade paths.

Identify the family, patch and hot fixes actually installed. According to MS-ISAC, four of the five flaws do not require authentication. A hosted instance, partner environment and self-managed integration may not follow the same maintenance path.

Patch and confirm the state

Ask the team operating the instance to confirm the update, then verify the level in the console and change records. For partner or self-managed environments, follow KB3159623 and the applicable upgrade instructions.

Preserve useful evidence before changing access rules or data. General security guidance does not replace confirmation of the installed patch.

Data, integrations and privilege

Map administrator roles, API integrations and the tables or workflows reachable by AI Platform. Look for new accounts, privilege changes, unusual API calls and data modifications that do not match a planned operation.

On September 25, MS-ISAC reported no known in-the-wild exploitation. Treat that statement as dated visibility, not as a guarantee for an unverified instance.

How Soclyde fits

Soclyde does not patch ServiceNow or determine whether an instance was used by a third party. It can help organise administrator access and integration secrets in an encrypted local-first vault, with a distinct value for each service.

That organisation reduces secret copies during an access review without replacing role controls, logs or ServiceNow remediation. To organize integration credentials, read our team password-sharing guide and password-manager security audit.

The takeaway

ServiceNow fixed five AI Platform CVEs; required versions differ across Australia, Yokohama and Zurich. Confirm the exact hot fix and instance actions, then review access and data. Read the secure password generator guide or contact Soclyde.

Frequently asked questions

Which ServiceNow versions are affected?

Fixed levels are Australia Patch 2 Hot Fix 4b W32, Australia Patch 4 Hot Fix 3 or Patch 5; Yokohama Patch 13 Hot Fix 5a; and Zurich Patch 10 Hot Fix 3b, Patch 10 Hot Fix 4a W32 or Patch 11 Hot Fix 3. Use the threshold for your release branch.

Are these vulnerabilities being exploited?

On September 25, 2026, MS-ISAC reported no known in-the-wild exploitation. This is a point-in-time statement, not a current guarantee or a reason to delay patching.

What should teams check after patching?

Confirm the fix for your release branch, then review privileged accounts, API calls and data changes. Look for accounts created or data read, changed or deleted without authorization.

References

Sources and references

Need advice?

Design your password strategy with Soclyde

Schedule a dedicated walkthrough with the team to see how local-first security adapts to your stack.

Talk with us

Keep reading