From the NetApp edition of October 31, 2026
NetApp advisory NTAP-20261023-0001 (v8.0): actively exploited Brotli flaw affects Console Agent containers and ONTAP Select Deploy; no fixes listed; AIDE and ONTAP 9 not affected
NetApp (Product Security) · Strategic partner: management-plane and data-services security · Global
- Publisher
- NetApp Product Security
- Original publication
- Initial release 10/23/2026; version 8.0 last updated 10/30/2026
- Source retrieved
- 2026-11-01
- Event date
- 2026-10-23
What happened
NetApp's advisory for CVE-2026-111497, a Google Brotli decoder flaw that NetApp says is also known as Node2Shell or HTTP2Shell and scores CRITICAL 9.2, was at version 8.0 on 10/30/2026 with status Interim. Listed as affected: NetApp Console Agent Container (audit), Console Agent Container (e-series) and the ONTAP Select Deploy administration utility. Under investigation: the Console Agent OVA, eleven other Console Agent containers, Data Classification, SolidFire/HCI, XCP and others. Version 8.0 moved six Console Agent containers into that status. ONTAP 9, AI Data Engine, the AIDE MCP Server and the AIDE LangChain Retriever are listed as not affected. The remediation tab lists no patches and no workarounds. Independently, CISA added CVE-2026-111497 to its Known Exploited Vulnerabilities catalog on October 27 based on evidence of active exploitation.
Why it matters
SLED teams running NetApp Console agents, which Console documentation ties to Cloud Volumes ONTAP deployments and the AIDE requirements tie to AIDE, now have a KEV-listed flaw in components with no NetApp fix listed. State and local agencies that follow CISA KEV prioritization, and universities with similar policies, will need compensating controls and tracking for these components even though ONTAP 9 itself is not affected.
Evidence and measured results
Vendor advisory with product status lists and revision history (1.0 on 10/23 through 8.0 on 10/30). Independent corroboration of exploitation comes from CISA's 10/27 KEV alert and the Canadian Centre for Cyber Security alert AL26-027 (10/28), neither of which mentions NetApp. NetApp's Console what's-new page lists no Console agent release after 4.11.0 (16 September). Its 15 October entry did not render.
Limitations and uncertainty
Vendor-authored and Interim; the advisory went through eight versions in a week. NetApp gives no NetApp-specific exploitation evidence. CISA and CCCS describe Brotli generally. The page is JavaScript-rendered. First-time source, not in the archive. The 10-30 edition covered the separate PHP2SHELL and MySQL advisories.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-01; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Customers depend on Console agents that now carry a KEV-listed vulnerability with no vendor fix listed.
- Stakeholders
- CISO or security operations lead
- Storage and cloud operations team
- Vulnerability management coordinator
- Account partner or MSP
- Discovery questions
- Where are Console agents deployed and in what form?
- Does the customer use ONTAP Select Deploy?
- Does policy require KEV remediation deadlines or documented exceptions?
- Are AIDE or Cloud Volumes ONTAP pilots planned that add agents?
- Value hypothesis
- A quick exposure review helps customers meet KEV-driven policy obligations while waiting for NetApp fixes.
- Potential engagement
- Bounded exposure review of Console agents and ONTAP Select Deploy with compensating-control recommendations and advisory tracking.
- Unsupported claims
- Customers are already compromised
- ONTAP arrays are affected
- A fix is available
- NetApp-specific exploitation has occurred
Pre-sales engineering
Role takeaway
- Fit
- Applies wherever Console agents (OVA or container) or ONTAP Select Deploy are present.
- Architecture and integration
- Console agent bridges NetApp Console with ONTAP and AIDE; ONTAP Select Deploy manages software-defined ONTAP.
- Prerequisites
- Inventory of agents and Select Deploy instances
- Network path documentation for agent hosts
- Access to advisory updates
- Constraints
- No patches or workarounds listed as of v8.0
- Many agent containers still under investigation
- Advisory does not state attack preconditions for NetApp components
- Security
- Limit inbound exposure of agent and Deploy hosts, monitor for crashes and anomalies, and prioritize under KEV policy.
- Proof of value
- Verify no agent host accepts untrusted inbound connections
- Confirm monitoring alerts on agent process crashes
- Track advisory revisions until a fixed agent build is listed
Delivery
Role takeaway
- Work
- Inventory, apply compensating controls, document exceptions and schedule upgrades when fixes appear.
- Dependencies
- NetApp fixed release
- Customer change windows
- Security exception process
- Ownership
- Security operations owns tracking and exceptions; storage or cloud operations owns agent upgrades.
- Skills and adoption
- Operations staff need the Console agent upgrade procedure and a habit of advisory revision checks.
- Governance checkpoints
- Documented KEV exception or compensating control
- Review at each advisory revision
- Post-upgrade verification
- Acceptance criteria
- Proposed: all agents inventoried with versions
- Proposed: compensating controls documented for each affected component
- Proposed: upgrade completed within the customer KEV window after a fix is published
- Risks
- Fix delays beyond policy deadlines
- Under-investigation components later confirmed affected
- New AIDE pilots adding exposed agents
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
The Console agent sits between NetApp Console and on-premises or cloud ONTAP and, per the AIDE requirements, exchanges traffic with AIDE. Exposure depends on whether affected containers process untrusted Brotli-compressed input; NetApp does not say. Agents should not be internet-exposed beyond documented outbound needs.
Governance
Who approves, reviews and stays accountable for outcomes?
KEV listing with no vendor fix triggers exception handling under many state vulnerability policies. Agencies should record risk acceptance or compensating controls and track the Interim advisory through further revisions.
Security and privacy
What data, permissions and controls need testing?
CCCS advises blocking untrusted Brotli-compressed input and monitoring for crashes where patching is not possible. For NetApp components this means restricting inbound reach to Console agent hosts and ONTAP Select Deploy, and watching NetApp for fixed agent releases.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Adds security-operations tracking work; no accessibility content in the source.
Procurement
What should contracts, pricing and exit terms secure?
Managed-service or support contracts should define who tracks vendor advisories and applies agent fixes.
Operating model
Which teams own the service once it runs?
Console agents are now part of the patch-critical estate alongside ONTAP, so SaaS-managed components need the same advisory discipline.
Publication history
- 2026-10-31NetApp · Issue 033 resources
Stable resource ID: netapp-advisory-ntap-20261023-0001-brotli-console-agent-20261030