Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-88811 is a critical-severity Insertion of Sensitive Information Into Sent Data (CWE-201) vulnerability. Its CVSS base score is 9.1 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Valid Accounts (T1078); ranked at the 37th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-115330
Vulnerability Data
Missing filtering in the SUSE Rancher Manager meta proxy could cause passed in rancher credentials to be leaked to cloud providers. This affects SUSE Rancher 2.15.0 up to 2.15.3, 2.14.0 up to 2.14.7, 2.13.0 up to 2.13.11,
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 1 hardening rule · 1 OS baseline
V14.2.3
Mitigating Controls (NIST 800-53 r5)
Our mappings, made for this CVE.
Enforces authorizations on logical access so that sensitive data is not released to unauthorized recipients.
Directly enforces policy-based information flow rules that block transmission of sensitive data to unauthorized actors.
Requires validation of outbound information to ensure sensitive content is not disclosed in responses or messages.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Secure SDLC practices directly prevent insertion of sensitive data into application outputs and messages.
Monitoring runtime data flows and outputs can detect sensitive data being transmitted.
Protecting data-in-transit can include filtering or encrypting to avoid exposing sensitive content.
Protecting data-in-use includes removing confidential values before they are processed or sent.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
Data-masking techniques can prevent sensitive values from appearing in transmitted payloads.
A.8.29's SOURCE+RUNTIME reach covers CWE-201 well: code review and static analysis can spot sensitive fields being placed in response objects, and penetration testing/dynamic analysis can observe the data actually leaving the system (the weakness is by definition visible to another actor receiving the response). The remainder is bounded and nameable — cases where the sensitivity classification depends on business context the tester cannot infer (e.g., the 'show email address' setting example), or response paths the test plan does not exercise.
A.5.26's post-incident root-cause analysis (items i and j) can identify CWE-201 as the weakness behind a detected data-leakage incident, but the programme only reaches instances that have caused a noticed incident and been investigated to the code level — a minority of latent CWE-201 instances, since most silent data-sending weaknesses never surface as incidents.
A.8.12's DLP tools can detect and block outbound transmissions containing sensitive data patterns (e.g., credentials in error messages, email addresses in API responses), masking the code defect during egress, but the application-level weakness remains and many instances — internal transmissions, novel data formats like heap addresses, legitimate API responses to authorized recipients within the trust boundary — fall outside DLP's monitored channels.
Secure-coding standards explicitly forbid hard-coded or unfiltered sensitive data in outbound messages.
A.8.5 prevents sensitive authentication-related data such as passwords and pre-login system details from being inserted into logon traffic, but its scope is authentication and it does not reach the broader class of sensitive information embedded in other application responses or error messages.