Comparison Overview
Old Navy

Old Navy
2 Folsom Street, San Francisco, 94158, US
Last Update: 01/04/2026
Forget what you know about old-school industry rules. When you work at Old Navy, you’re choosing a different path. From day one, we’ve been on a mission to democratize fashion and make shopping fun again. Our teams make style accessible to everyone, creating high-qualit...

Next
Enderby, Leicester, Leicestershire, GB, LE19 4AT
Last Update: 05/06/2026
At Next we never underestimate what we can do. Bring your energy, play to your strengths and never shy away from change. Push yourself and back others. Make things happen that will be bigger and better than before. Come and work for one of the UK’s biggest retailers. ...
Compliance Ranges Comparison

Old Navy







Next






Benchmark & Cyber Underwriting Signals
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Old Navy in 2026.
Incidents vs Retail Industry Avg (This Year)
No incidents recorded for Next in 2026.
Incident History - Old Navy (X = Date, Y = Severity)
Old Navy cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Next (X = Date, Y = Severity)
Next cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Old Navy

Next
FAQ
Latest Global CVEs
Fides is an open-source privacy engineering platform. From version 2.33.0 to before version 2.84.5, there is a DOM-based XSS vulnerability in fides.js via the fides_description override. This issue has been patched in version 2.84.5.
WACRM prior to commit 73041bf contain an authorization bypass vulnerability in the automation engine that allows authenticated attackers to access and modify contacts belonging to other tenants by supplying an arbitrary caller-controlled contact_id in the POST request body without tenant ownership verification. Attackers can exploit the service-role client that bypasses row-level security to modify victim contact fields including name, email, and company across tenant boundaries using only a known contact UUID.
Namespace attributes are not encoded correctly during HTML serialization. This allows bypassing the cross-site scripting prevention mechanism of typo3/html-sanitizer before version 2.3.2.
When ALLOW_INSECURE_RAW_TEXT is enabled, whitespace-variant closing tags (e.g., </style\t>) are not recognized by the sanitizer but accepted by browsers as valid end tags, allowing subsequent content to escape sanitization. This allows bypassing the cross-site scripting prevention mechanism of typo3/html-sanitizer before version 2.3.2.
Headplane is a feature-complete Web UI for Headscale. Prior to versions 0.6.3 and 0.7.0-beta.3, Headplane was vulnerable to a path traversal / authorization bypass in the Headscale API client used by node and user rename operations. This issue has been patched in versions 0.6.3 and 0.7.0-beta.3.