Incidentsby IbisTenable Vulnerability Management / Tenable One / Tenable Cloud Security / Tenable Security Center / Tenable OT Security / Nessus: Incorrect VPR Scores Calculated
May 28, 19:11 UTCMay 27, 15:00 UTC
Duration
0m
Impact
Informational
Root cause
Not disclosed
Tenable, 90 days
28 incidents
Affected
Not listed by the vendor.
Final update
Between 3:00PM UTC May 27 2026 to 5:00PM UTC May 28 2026 UTC, certain users could have experienced incorrect VPR scores calculated to the feed. The incorrect scores that may have been populated during that time are being corrected but any exports taken may still be incorrect. The underlying issue has been resolved and corrective actions are being taken to correct the affected data over the next day. We are sorry for the disruption and inconvenience.
Timeline
- Resolved · May 27, 15:00 UTC
Between 3:00PM UTC May 27 2026 to 5:00PM UTC May 28 2026 UTC, certain users could have experienced incorrect VPR scores calculated to the feed. The incorrect scores that may have been populated during that time are being corrected but any exports taken may still be incorrect. The underlying issue has been resolved and corrective actions are being taken to correct the affected data over the next day. We are sorry for the disruption and inconvenience.
More from Tenable
Full historyTenable Vulnerability Management: Unresponsive Cyber Exposure Feedlasted 0mTenable One: Delay in Tenable Exposure Management datalasted 2d 5hTenable Patch management: Possible GUI slowness along with 502/503 Errors Observedlasted 2dTenable Vulnerability Management: Scan processing and Explore Findings and Asset pages delayslasted 3h 39mTenable Patch management: Possible GUI slowness along with 502/503 Errors Observedlasted 3d 14hTenable Vulnerability Management: Scheduled Scans Not Launchinglasted 13h 16m