Retrospective for 2026-10-27, compiled on 27 October 2026. The date identifies the day being analysed; source publication and revision dates are recorded below.
What this advisory changes in your environment
The starting point is CERTFR-2026-AVI-1383, published on 2026-10-26. Its scope includes Microsoft Visual Studio 2026, PowerShell 7.6, Microsoft Visual Studio 2019, Microsoft Visual Studio 2022, PowerShell 7.5, PowerShell 7.4. Reported consequences are privilege escalation. These statements apply to the advisory’s scope; they do not assign every consequence to every product or CVE.
This case contains 7 version entries; CVE identifier count: 1. Track remediation by component: a successful overall update does not demonstrate that Microsoft Visual Studio 2026 and PowerShell 7.4 each received their respective fix.
Products and versions to examine
- Reference
- CERTFR-2026-AVI-1383
- Source first published
- 2026-10-26
- Latest source revision available for this day
- 2026-10-26
- Named components
- Microsoft Visual Studio 2026, PowerShell 7.6, Microsoft Visual Studio 2019, Microsoft Visual Studio 2022, PowerShell 7.5, PowerShell 7.4
- CVE identifiers
- CVE-2026-111497
| Component | Published condition |
|---|---|
| Microsoft Visual Studio 2026 | 18.12 : < 18.12 Insiders 3 |
| PowerShell 7.6 | < 7.6.9 |
| Microsoft Visual Studio 2019 | 16.11 : < 16.11.61 |
| Microsoft Visual Studio 2022 | 17.14 : < 17.14.43 |
| Microsoft Visual Studio 2026 | 18.11 : < 18.11.2 |
| PowerShell 7.5 | < 7.5.13 |
| PowerShell 7.4 | < 7.4.22 |
For Microsoft Visual Studio 2026, the published condition is “18.12 : < 18.12 Insiders 3”. Compare the version actually loaded with that condition within its own release branch. A fix installed on another edition of Microsoft Visual Studio 2026 does not close this case.
Mechanism and prerequisites
Privilege escalation expands an existing foothold into greater permissions. Examine boundaries between ordinary accounts, services and administrators, and retain evidence of role changes.
The primary record CVE-2026-111497, published by Google, covers Brotli. The retained revision is dated 2026-10-26. Its scope is presented separately from the integrations and product groupings in CERTFR-2026-AVI-1383.
The published metric for CVE-2026-111497 is CVSS 4.0, 9.2/10. The vector below describes technical prerequisites; it does not measure attack frequency or the likelihood that your deployment is compromised.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- Attack vector
- network
- Prior privileges
- none
- User interaction
- none
- Complexity
- low
- Additional attack requirements
- present
- Weakness
- CWE-787, CWE-252
Choose the appropriate intervention
- Locate Microsoft Visual Studio 2026 instances, running releases and service owners. Record condition 18.12 : < 18.12 Insiders 3 in the ticket alongside reference CERTFR-2026-AVI-1383.
- Compare the installed branch with the vendor’s Microsoft Visual Studio 2026 release notes. Prepare the package for that branch and a dependent-service test, retaining the pre-change state.
- After changing Microsoft Visual Studio 2026, capture the loaded version again and verify the workflow below. Any exception needs an owner, an exposure-reduction measure and an expiry date.
Verify the fix in a real workflow
Validation scenario to adapt for Microsoft Visual Studio 2026: In a test project using Microsoft Visual Studio 2026, rerun a build without production secrets and verify the delivered artifact. Compare runner permissions, actually resolved dependencies and the behaviour of a contributor without an administrative role. This is a proposed defensive check, not a claim that testing was performed against third-party systems.
Limit of case CERTFR-2026-AVI-1383: this analysis replaces neither vendor prerequisites nor investigation of your logs. Only documented versions are reproduced; no attack date or victim is invented.
Questions specific to this case
Which condition should be checked for Microsoft Visual Studio 2026?
Advisory CERTFR-2026-AVI-1383 states: Microsoft Visual Studio 2026 — 18.12 : < 18.12 Insiders 3. Check the edition and running release; do not extend the published boundary to branches absent from the advisory.
Why not use one fix for Microsoft Visual Studio 2026 and PowerShell 7.4?
CERTFR-2026-AVI-1383 distinguishes these components within a scope containing 7 entries. Match each branch to its own update documentation and functional check.
Which prerequisites does record CVE-2026-111497 specify?
For CVE-2026-111497, the published vector is CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N. Verify those conditions on Brotli before applying them to an integration named in CERTFR-2026-AVI-1383.
Sources and related reading
Practical guide : Software supply chain assurance: components to release
Explore the decision addressed in this case
Complete source advisory inventory
The article table may be an extract. These lists contain every affected-system entry and CVE in the specified advisory revision. They are not an inventory of your assets and do not map every CVE to every product.
Official source · CERTFR-2026-AVI-1383
Advisory revision : · Checked on :
Affected systems · 7
Original French wording is retained to avoid ambiguous translations of version conditions.
- Microsoft Visual Studio 2026 version 18.12 antérieures à 18.12 Insiders 3
- PowerShell 7.6 versions antérieures à 7.6.9
- Microsoft Visual Studio 2019 version 16.11 antérieures à 16.11.61
- Microsoft Visual Studio 2022 version 17.14 antérieures à 17.14.43
- Microsoft Visual Studio 2026 version 18.11 antérieures à 18.11.2
- PowerShell 7.5 versions antérieures à 7.5.13
- PowerShell 7.4 versions antérieures à 7.4.22