Live  /  Tenable  /  Incident

Tenable: Tenable Vulnerability Management: RBAC Permissions Issue with Custom Roles

Tenable · tenable.comMajor incidentResolved2026-10-13 07:49 UTC
Public — what happened

Summary

Tenable said that starting on 2026-10-06 at 22:19 UTC, some Tenable Vulnerability Management users who had custom PCI roles could not reach certain settings. The company reported finding the cause on 2026-10-08 but did not describe it publicly, and it said a fix was put in place on 2026-10-09. Tenable noted that where custom roles had lost Platform Settings access, an administrator would have to restore those permissions by hand using steps in its knowledge base. The incident was marked resolved on 2026-10-13.

Affected

US-1A, US-2A, US-2B, US-3A, US-4A, US-5A, US07, US08, AP-SYD-1, BR01, CA01, FRA, IN01, JP01, UK-LON-1, SING, GOV01, ca02

As listed on Tenable’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Tenable against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Tenable: its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Tenable report →

More from Tenable

Covered in The Squid’s Ink, Week 42, 2026, our weekly internet health report.

The full archive is on the Tenable status & history page.

Related: Tenable status & history. SquidGrid is not affiliated with Tenable.