{"items":[{"id":"NVI-00001823","kind":"vulnerability","title":"HTTP Host Header Injection","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-m2jh-fxw4-gphm","CVE-2021-41114"],"plain_summary":"OSV carries this publisher advisory for typo3/cms-core, typo3/cms. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 11.5.0 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-01b79cfdc3400fa34f54fcd8d9dd87fb"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 11.5.0 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-01b79cfdc3400fa34f54fcd8d9dd87fb"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-0f55c3f986f01dbf737db43686378b07"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-11-03T12:00:27.000Z","value":"1.221%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.68744. Missing scores are unknown.","source_id":"sr-0f55c3f986f01dbf737db43686378b07"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-01b79cfdc3400fa34f54fcd8d9dd87fb","url":"https://github.com/advisories/GHSA-m2jh-fxw4-gphm","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-m2jh-fxw4-gphm","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.971Z"},{"id":"sr-0f55c3f986f01dbf737db43686378b07","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2021-41114","publisher":"FIRST EPSS","observed_at":"2026-11-03T17:42:56.080Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-01b79cfdc3400fa34f54fcd8d9dd87fb"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Meta\n* CVSS: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N/E:F/RL:O/RC:C` (3.5)\n\n### Problem\nIt has been discovered that TYPO3 CMS is susceptible to host spoofing due to improper validation of the HTTP _Host_ header. TYPO3 uses the HTTP _Host_ header, for example, to generate absolute URLs during the frontend rendering process. Since the host header itself is provided by the client, it can be forged to any value, even in a name-based virtual hosts environment.\n\nThis vulnerability is the same as described in TYPO3-CORE-SA-2014-001 (CVE-2014-3941). A regression, introduced during TYPO3 v11 development, led to this situation. The already existing setting _$GLOBALS['TYPO3_CONF_VARS']['SYS']['trustedHostsPattern']_ (used as an effective mitigation strategy in previous TYPO3 versions) was not evaluated anymore, and reintroduced the vulnerability.\n\n### Solution\nUpdate your instance to TYPO3 version 11.5.0 which addresses the problem described.\n\n### Credits\nThanks to TYPO3 framework merger Benjamin Franzke who reported and fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2021-015](https://typo3.org/security/advisory/typo3-","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.0"]},{"certainty":"source_listed","source_ids":["sr-01b79cfdc3400fa34f54fcd8d9dd87fb"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"### Meta\n* CVSS: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N/E:F/RL:O/RC:C` (3.5)\n\n### Problem\nIt has been discovered that TYPO3 CMS is susceptible to host spoofing due to improper validation of the HTTP _Host_ header. TYPO3 uses the HTTP _Host_ header, for example, to generate absolute URLs during the frontend rendering process. Since the host header itself is provided by the client, it can be forged to any value, even in a name-based virtual hosts environment.\n\nThis vulnerability is the same as described in TYPO3-CORE-SA-2014-001 (CVE-2014-3941). A regression, introduced during TYPO3 v11 development, led to this situation. The already existing setting _$GLOBALS['TYPO3_CONF_VARS']['SYS']['trustedHostsPattern']_ (used as an effective mitigation strategy in previous TYPO3 versions) was not evaluated anymore, and reintroduced the vulnerability.\n\n### Solution\nUpdate your instance to TYPO3 version 11.5.0 which addresses the problem described.\n\n### Credits\nThanks to TYPO3 framework merger Benjamin Franzke who reported and fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2021-015](https://typo3.org/security/advisory/typo3-","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.0"]}],"null_published_at":"2026-11-06T00:29:57.276Z","source_updated_at":"2026-07-08T06:29:06.518Z","source_disclosed_at":"2021-10-05T20:23:35.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:42:30.971Z"},{"id":"NVI-00001823","kind":"vulnerability","title":"HTTP Host Header Injection","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-m2jh-fxw4-gphm","CVE-2021-41114"],"plain_summary":"OSV carries this publisher advisory for typo3/cms-core, typo3/cms. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 11.5.0 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-01b79cfdc3400fa34f54fcd8d9dd87fb"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 11.5.0 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-01b79cfdc3400fa34f54fcd8d9dd87fb"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-03933b25b20966430d71ba60b3cd095e"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-11-02T12:00:30.000Z","value":"1.221%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.68711. Missing scores are unknown.","source_id":"sr-03933b25b20966430d71ba60b3cd095e"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-01b79cfdc3400fa34f54fcd8d9dd87fb","url":"https://github.com/advisories/GHSA-m2jh-fxw4-gphm","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-m2jh-fxw4-gphm","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.971Z"},{"id":"sr-03933b25b20966430d71ba60b3cd095e","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2021-41114","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:14:50.774Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-01b79cfdc3400fa34f54fcd8d9dd87fb"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Meta\n* CVSS: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N/E:F/RL:O/RC:C` (3.5)\n\n### Problem\nIt has been discovered that TYPO3 CMS is susceptible to host spoofing due to improper validation of the HTTP _Host_ header. TYPO3 uses the HTTP _Host_ header, for example, to generate absolute URLs during the frontend rendering process. Since the host header itself is provided by the client, it can be forged to any value, even in a name-based virtual hosts environment.\n\nThis vulnerability is the same as described in TYPO3-CORE-SA-2014-001 (CVE-2014-3941). A regression, introduced during TYPO3 v11 development, led to this situation. The already existing setting _$GLOBALS['TYPO3_CONF_VARS']['SYS']['trustedHostsPattern']_ (used as an effective mitigation strategy in previous TYPO3 versions) was not evaluated anymore, and reintroduced the vulnerability.\n\n### Solution\nUpdate your instance to TYPO3 version 11.5.0 which addresses the problem described.\n\n### Credits\nThanks to TYPO3 framework merger Benjamin Franzke who reported and fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2021-015](https://typo3.org/security/advisory/typo3-","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.0"]},{"certainty":"source_listed","source_ids":["sr-01b79cfdc3400fa34f54fcd8d9dd87fb"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"### Meta\n* CVSS: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N/E:F/RL:O/RC:C` (3.5)\n\n### Problem\nIt has been discovered that TYPO3 CMS is susceptible to host spoofing due to improper validation of the HTTP _Host_ header. TYPO3 uses the HTTP _Host_ header, for example, to generate absolute URLs during the frontend rendering process. Since the host header itself is provided by the client, it can be forged to any value, even in a name-based virtual hosts environment.\n\nThis vulnerability is the same as described in TYPO3-CORE-SA-2014-001 (CVE-2014-3941). A regression, introduced during TYPO3 v11 development, led to this situation. The already existing setting _$GLOBALS['TYPO3_CONF_VARS']['SYS']['trustedHostsPattern']_ (used as an effective mitigation strategy in previous TYPO3 versions) was not evaluated anymore, and reintroduced the vulnerability.\n\n### Solution\nUpdate your instance to TYPO3 version 11.5.0 which addresses the problem described.\n\n### Credits\nThanks to TYPO3 framework merger Benjamin Franzke who reported and fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2021-015](https://typo3.org/security/advisory/typo3-","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.0"]}],"null_published_at":"2026-11-03T17:49:14.996Z","source_updated_at":"2026-07-08T06:29:06.518Z","source_disclosed_at":"2021-10-05T20:23:35.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:42:30.971Z"},{"id":"NVI-00001823","kind":"vulnerability","title":"HTTP Host Header Injection","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-m2jh-fxw4-gphm","CVE-2021-41114"],"plain_summary":"OSV carries this publisher advisory for typo3/cms-core, typo3/cms. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 11.5.0 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-01b79cfdc3400fa34f54fcd8d9dd87fb"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 11.5.0 for typo3/cms. Confirm the publisher’s latest guidance.","source_ids":["sr-01b79cfdc3400fa34f54fcd8d9dd87fb"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-01b79cfdc3400fa34f54fcd8d9dd87fb","url":"https://github.com/advisories/GHSA-m2jh-fxw4-gphm","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-m2jh-fxw4-gphm","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.971Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-01b79cfdc3400fa34f54fcd8d9dd87fb"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Meta\n* CVSS: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N/E:F/RL:O/RC:C` (3.5)\n\n### Problem\nIt has been discovered that TYPO3 CMS is susceptible to host spoofing due to improper validation of the HTTP _Host_ header. TYPO3 uses the HTTP _Host_ header, for example, to generate absolute URLs during the frontend rendering process. Since the host header itself is provided by the client, it can be forged to any value, even in a name-based virtual hosts environment.\n\nThis vulnerability is the same as described in TYPO3-CORE-SA-2014-001 (CVE-2014-3941). A regression, introduced during TYPO3 v11 development, led to this situation. The already existing setting _$GLOBALS['TYPO3_CONF_VARS']['SYS']['trustedHostsPattern']_ (used as an effective mitigation strategy in previous TYPO3 versions) was not evaluated anymore, and reintroduced the vulnerability.\n\n### Solution\nUpdate your instance to TYPO3 version 11.5.0 which addresses the problem described.\n\n### Credits\nThanks to TYPO3 framework merger Benjamin Franzke who reported and fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2021-015](https://typo3.org/security/advisory/typo3-","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.0"]},{"certainty":"source_listed","source_ids":["sr-01b79cfdc3400fa34f54fcd8d9dd87fb"],"technology":"typo3/cms","known_exclusions":[],"conditions_summary":"### Meta\n* CVSS: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N/E:F/RL:O/RC:C` (3.5)\n\n### Problem\nIt has been discovered that TYPO3 CMS is susceptible to host spoofing due to improper validation of the HTTP _Host_ header. TYPO3 uses the HTTP _Host_ header, for example, to generate absolute URLs during the frontend rendering process. Since the host header itself is provided by the client, it can be forged to any value, even in a name-based virtual hosts environment.\n\nThis vulnerability is the same as described in TYPO3-CORE-SA-2014-001 (CVE-2014-3941). A regression, introduced during TYPO3 v11 development, led to this situation. The already existing setting _$GLOBALS['TYPO3_CONF_VARS']['SYS']['trustedHostsPattern']_ (used as an effective mitigation strategy in previous TYPO3 versions) was not evaluated anymore, and reintroduced the vulnerability.\n\n### Solution\nUpdate your instance to TYPO3 version 11.5.0 which addresses the problem described.\n\n### Credits\nThanks to TYPO3 framework merger Benjamin Franzke who reported and fixed the issue.\n\n### References\n* [TYPO3-CORE-SA-2021-015](https://typo3.org/security/advisory/typo3-","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.0"]}],"null_published_at":"2026-10-31T21:53:28.051Z","source_updated_at":"2026-07-08T06:29:06.518Z","source_disclosed_at":"2021-10-05T20:23:35.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:42:30.971Z"}],"next_cursor":null,"snapshot_revision":"42594"}