English edition · cyberattaques.org in FrenchFrançais
VulnerabilityPatch available

Microsoft Edge: CERT-FR flags dozens of vulnerabilities fixed on 13 November 2026

CERT-FR published an advisory on 16 November 2026 covering multiple Microsoft Edge vulnerabilities that Microsoft fixed in bulletins dated 13 November. Organisations running Edge on the 156 and 157 branches should check which build their endpoints use.

What to do now Illustration photo (network cables)
CVSS severity4.7Medium
EPSS probability0 %
ExploitationNot observed
PatchAvailable
Product
Microsoft Edge
Affected versions
Microsoft Edge 157.x prior to 157.0.4341.57; Microsoft Edge prior to 156.0.4314.80
Fixed in
157.0.4341.57; 156.0.4314.80
CVE
CVE-2026-125342

France's CERT-FR released advisory CERTFR-2026-AVI-1546 on 16 November 2026, covering a batch of vulnerabilities in the Microsoft Edge browser. It draws on several dozen Microsoft security bulletins issued on 13 November 2026, each tied to its own CVE identifier, including CVE-2026-125342.

Affected builds are Edge 157.x releases earlier than 157.0.4341.57 and any Edge version earlier than 156.0.4314.80. Endpoints running one of these builds are exposed.

Neither Microsoft nor CERT-FR describes the impact. The advisory only states that an attacker could trigger a security problem the vendor has not specified, and it does not report any active exploitation.

CERT-FR points readers to Microsoft's bulletins for the fixes. Based on the version ranges given, builds 157.0.4341.57 and 156.0.4314.80 contain the corrections. No workaround is described.

Edge usually updates itself, but fleets managed through group policy, environments with deferred updates, and machines that are rarely restarted can stay on a vulnerable build for days.

Action plan

What to do now

  1. Roll out Microsoft Edge 157.0.4341.57 to endpoints on the 157 branch, or at least 156.0.4314.80 to those still on the 156 branch.
  2. Use your inventory or endpoint management tool to confirm no machine still runs an earlier build.
  3. Make sure browsers are restarted after updating so the fixes actually take effect.
  4. Review the Microsoft bulletins listed in advisory CERTFR-2026-AVI-1546 for per-CVE details.

Sources