IBM Sterling Secure Proxy is vulnerable to multiple issues

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps IBM/Sterling Secure Proxy (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for IBM/Sterling Secure Proxy.
2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

1. Published upstream

   Sep 14, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Sep 14, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Sep 14, 2026

Sources and claim methodology

• Source referenceibm.com

Related CVEs

• IBM Sterling Secure Proxy is vulnerable to multiple issuesSame ibm/sterling secure proxy package
• Security vulnerabilities have been addressed in IBM Verify Identity Access and IBM Security Verify AccessAlso CWE-79
• Concrete CMS 9.0.0 to 9.5.2 is vulnerable to Stored XSS in Custom Page Alias NameAlso CWE-79
• IBM Cognos Analytics versions 12.0.4 and 12.1.3 is affected by security vulnerabilitiesAlso CWE-79
• Concrete CMS 9.0.0 to 9.5.2 is vulnerable to Stored XSS via Page Container iconAlso CWE-79
• Takahe through 0.11.0 Cross-Site Scripting via javascript: URL SchemeAlso CWE-79