Retrospective for 2026-06-08, 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-0702, published on 2026-06-08. Its scope includes Micrometer Core, Jetty11 et Jetty12, Micrometer, Micrometer Jetty11 et Jetty12. Reported consequences are denial of service. These statements apply to the advisory’s scope; they do not assign every consequence to every product or CVE.
This case contains 5 version entries; CVE identifier count: 2. Track remediation by component: a successful overall update does not demonstrate that Micrometer Core, Jetty11 et Jetty12 and Micrometer Jetty11 et Jetty12 each received their respective fix.
Products and versions to examine
- Reference
- CERTFR-2026-AVI-0702
- Source first published
- 2026-06-08
- Latest source revision available for this day
- 2026-06-08
- Named components
- Micrometer Core, Jetty11 et Jetty12, Micrometer, Micrometer Jetty11 et Jetty12
- CVE identifiers
- CVE-2026-40984, CVE-2026-40983
| Component | Published condition |
|---|---|
| Micrometer Core, Jetty11 et Jetty12 | 1.9.x : < 1.9.18 |
| Micrometer | 1.16.x : < 1.16.6 |
| Micrometer Jetty11 et Jetty12 | 1.13.x : < 1.13.19 |
| Micrometer | 1.15.x : < 1.15.12 |
| Micrometer Jetty11 et Jetty12 | 1.14.x : < 1.14.16 |
For Micrometer Core, Jetty11 et Jetty12, the published condition is “1.9.x : < 1.9.18”. Compare the version actually loaded with that condition within its own release branch. A fix installed on another edition of Micrometer Core, Jetty11 et Jetty12 does not close this case.
Mechanism and prerequisites
Denial of service may interrupt a component without establishing data theft. Assess business dependencies, recovery capabilities and resource limits; test failover without generating hostile production traffic.
For CERTFR-2026-AVI-0702, 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 Micrometer Core, Jetty11 et Jetty12 or the risk category alone.
Choose the appropriate intervention
- Locate Micrometer Core, Jetty11 et Jetty12 instances, running releases and service owners. Record condition 1.9.x : < 1.9.18 in the ticket alongside reference CERTFR-2026-AVI-0702.
- Compare the installed branch with the vendor’s Micrometer Core, Jetty11 et Jetty12 release notes. Prepare the package for that branch and a dependent-service test, retaining the pre-change state.
- After changing Micrometer Core, Jetty11 et Jetty12, 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 Micrometer Core, Jetty11 et Jetty12: For Micrometer Core, Jetty11 et Jetty12, capture the version loaded by the process or active kernel, then restart only as required by maintenance instructions. Check a dependent workflow and look for embedded copies in distributed images or executables. This is a proposed defensive check, not a claim that testing was performed against third-party systems.
Limit of case CERTFR-2026-AVI-0702: 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 Micrometer Core, Jetty11 et Jetty12?
Advisory CERTFR-2026-AVI-0702 states: Micrometer Core, Jetty11 et Jetty12 — 1.9.x : < 1.9.18. Check the edition and running release; do not extend the published boundary to branches absent from the advisory.
Why not use one fix for Micrometer Core, Jetty11 et Jetty12 and Micrometer Jetty11 et Jetty12?
CERTFR-2026-AVI-0702 distinguishes these components within a scope containing 5 entries. Match each branch to its own update documentation and functional check.
What is still needed to assess Micrometer Core, Jetty11 et Jetty12 exposure?
For Micrometer Core, Jetty11 et Jetty12, establish the running version, the path to the component and process permissions. The sources retained for CERTFR-2026-AVI-0702 do not establish every prerequisite or active exploitation.
Sources and related reading
- CERT-FR · CERTFR-2026-AVI-0702
- Vendor and remediation · spring.io
- Vendor and remediation · spring.io
Practical guide : Prioritize vulnerabilities and verify remediation
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-0702
Advisory revision : · Checked on :
Affected systems · 5
Original French wording is retained to avoid ambiguous translations of version conditions.
- Micrometer Core, Jetty11 et Jetty12 versions 1.9.x antérieures à 1.9.18
- Micrometer versions 1.16.x antérieures à 1.16.6
- Micrometer Jetty11 et Jetty12 versions 1.13.x antérieures à 1.13.19
- Micrometer versions 1.15.x antérieures à 1.15.12
- Micrometer Jetty11 et Jetty12 versions 1.14.x antérieures à 1.14.16