Retrospective for 2026-10-13, 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-1299, published on 2026-10-13. Its scope includes Harmony STW6. Reported consequences are security control bypass. These statements apply to the advisory’s scope; they do not assign every consequence to every product or CVE.
This case focuses on Harmony STW6. Locate that edition in live installations, deployment images and actual dependencies, rather than treating every product from Schneider Electric as equivalent.
Products and versions to examine
- Reference
- CERTFR-2026-AVI-1299
- Source first published
- 2026-10-13
- Latest source revision available for this day
- 2026-10-13
- Named components
- Harmony STW6
- CVE identifiers
- CVE-2026-96434
Mechanism and prerequisites
A security bypass challenges a trust boundary. Verify server-side authorisation decisions and alternative paths; hiding an interface is not an access restriction.
For CERTFR-2026-AVI-1299, the retained documents do not provide a suitably dated primary CVE record to establish this case’s prerequisites. Required authentication, user interaction and active exploitation therefore remain unestablished here; they are not inferred from Harmony STW6 or the risk category alone.
Choose the appropriate intervention
- Locate Harmony STW6 instances, running releases and service owners. Record condition Not specified in the retained source in the ticket alongside reference CERTFR-2026-AVI-1299.
- Compare the installed branch with the vendor’s Harmony STW6 release notes. Prepare the package for that branch and a dependent-service test, retaining the pre-change state.
- After changing Harmony STW6, 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 Harmony STW6: For Harmony STW6, prepare validation with the operations owner on a test bench or representative copy. Verify process communications and maintenance access; technical ability to update does not authorise interruption of an industrial system. This is a proposed defensive check, not a claim that testing was performed against third-party systems.
Limit of case CERTFR-2026-AVI-1299: 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 Harmony STW6?
Advisory CERTFR-2026-AVI-1299 states: Harmony STW6 — Not specified in the retained source. Check the edition and running release; do not extend the published boundary to branches absent from the advisory.
What is still needed to assess Harmony STW6 exposure?
For Harmony STW6, establish the running version, the path to the component and process permissions. The sources retained for CERTFR-2026-AVI-1299 do not establish every prerequisite or active exploitation.
Sources and related reading
Practical guide : Software inventory: prepare for end of support
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-1299
Advisory revision : · Checked on :
Affected systems · 1
Original French wording is retained to avoid ambiguous translations of version conditions.
- Harmony STW6 toutes versions pour la vulnérabilité CVE-2026-96434