CVE-2026-100870
validatingZero is analyzing and reversing it now.GHSA-753f-ggfx-2h8w ↗EUVD-2026-87942 ↗
description
Sylius administrator password-reset emails may contain a reset link whose host is derived from an untrusted inbound request. An unauthenticated attacker who knows an administrator email address can request a reset and, if the administrator follows the altered link, obtain the reset token and potentially take over that administrator account.
Still under analysis: more detail becomes available as the pipeline runs.
mitigation
Upgrade sylius/sylius to 1.12.25, 1.13.17, 1.14.20, 2.1.16, 2.2.9, or a later compatible release; update any overridden administrator reset-email template to use the patched reset URL handling. Configure Symfony trusted hosts and reject unknown Host headers at the front-end server.
fixed in 1.12.25, 1.13.17, 1.14.20, 2.1.16, 2.2.9
outcome
Run in progress: no artifact yet.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-09-27 13:09Zghsa: trigger signal, started the run
- 2026-09-27 13:09Zcve.org record for CVE-2026-100870
this entry in the feed
GET /api/v1/feed/CVE-2026-100870
{ "etk_id": "ETK-2026-5014", "cve_id": "CVE-2026-100870", "display_id": "CVE-2026-100870", "ghsa_id": "GHSA-753f-ggfx-2h8w", "euvd_id": "EUVD-2026-87942", "status": "in_pipeline", "anchor_state": "anchored", "title": "Host header injection in Sylius administrator password-reset emails", "summary": "Sylius administrator password-reset emails may contain a reset link whose host is derived from an untrusted inbound request. An unauthenticated attacker who knows an administrator email address can request a reset and, if the administrator follows the altered link, obtain the reset token and potentially take over that administrator account.", "mitigation": "Upgrade sylius/sylius to 1.12.25, 1.13.17, 1.14.20, 2.1.16, 2.2.9, or a later compatible release; update any overridden administrator reset-email template to use the patched reset URL handling. Configure Symfony trusted hosts and reject unknown Host headers at the front-end server.", "vendor": null, "product": "composer:sylius/sylius", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 1.12.0, <= 1.12.24" ], "ecosystem": "composer", "fixed_versions": [ "1.12.25" ], "package_name": "sylius/sylius", "purl": "pkg:composer/sylius/sylius" }, { "affected_notes": [], "affected_ranges": [ ">= 1.13.0, <= 1.13.16" ], "ecosystem": "composer", "fixed_versions": [ "1.13.17" ], "package_name": "sylius/sylius", "purl": "pkg:composer/sylius/sylius" }, { "affected_notes": [], "affected_ranges": [ ">= 1.14.0, <= 1.14.19" ], "ecosystem": "composer", "fixed_versions": [ "1.14.20" ], "package_name": "sylius/sylius", "purl": "pkg:composer/sylius/sylius" }, { "affected_notes": [], "affected_ranges": [ ">= 2.0.0, <= 2.0.18" ], "ecosystem": "composer", "fixed_versions": [], "package_name": "sylius/sylius", "purl": "pkg:composer/sylius/sylius" }, { "affected_notes": [], "affected_ranges": [ ">= 2.1.0, <= 2.1.15" ], "ecosystem": "composer", "fixed_versions": [ "2.1.16" ], "package_name": "sylius/sylius", "purl": "pkg:composer/sylius/sylius" }, { "affected_notes": [], "affected_ranges": [ ">= 2.2.0, <= 2.2.8" ], "ecosystem": "composer", "fixed_versions": [ "2.2.9" ], "package_name": "sylius/sylius", "purl": "pkg:composer/sylius/sylius" } ], "cwes": [ 640 ], "cvss_score": 8.8, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H", "epss_score": null, "epss_percentile": null, "epss_asof": null, "automation": null, "check": false, "check_confidence_basis": null, "exploit": false, "pipeline_minutes": null, "t0_at": "2026-09-27T13:09:54.715000+00:00", "signals": { "trigger_signal": { "at": "2026-09-27T13:09:54.715000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-09-27T13:09:54.715000+00:00", "url": "https://github.com/Sylius/Sylius/security/advisories/GHSA-77w3-2367-7xvq" } } }
published 2026-11-20 06:46Z
last change 2026-11-20 06:46Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.