{"items":[{"id":"NVI-00008010","kind":"vulnerability","title":"symfony/ux-autocomplete: XSS via unescaped AJAX response data","revision":5,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-mwqm-4fw3-cjvr","CVE-2026-49216"],"plain_summary":"GitHub lists this reviewed advisory for symfony/ux-autocomplete, symfony/ux-autocomplete. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-214f12b444d2c4b7c0600acc35d21ae0"],"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},{"summary":"The original advisory lists fixed boundaries 2.36.0 for symfony/ux-autocomplete. Confirm the publisher’s latest guidance.","source_ids":["sr-f21c8a2ad9220aa6be0359e058268dc6"],"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 3.1.0 for symfony/ux-autocomplete. Confirm the publisher’s latest guidance.","source_ids":["sr-f21c8a2ad9220aa6be0359e058268dc6"],"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":[{"kind":"CVSS","as_of":"2026-10-24T20:10:00.137Z","value":"5.4 MEDIUM (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-34aef7ced2890aa096b3fb53f0527e3c"},{"kind":"CVSS","as_of":"2026-10-24T20:10:00.137Z","value":"5.1 MEDIUM (4.0)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-34aef7ced2890aa096b3fb53f0527e3c"},{"kind":"EPSS","as_of":"2026-11-02T12:00:30.000Z","value":"0.312%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.24053. Missing scores are unknown.","source_id":"sr-214f12b444d2c4b7c0600acc35d21ae0"}],"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-0cf1b4ad21c5be3a8b92259d29d2ee4e","url":"https://github.com/advisories/GHSA-mwqm-4fw3-cjvr","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-mwqm-4fw3-cjvr","publisher":"GitHub Advisory Database","observed_at":"2026-11-06T07:19:16.585Z"},{"id":"sr-f21c8a2ad9220aa6be0359e058268dc6","url":"https://github.com/advisories/GHSA-mwqm-4fw3-cjvr","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-mwqm-4fw3-cjvr","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.984Z"},{"id":"sr-34aef7ced2890aa096b3fb53f0527e3c","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-49216","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-49216","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-03T22:35:35.055Z"},{"id":"sr-214f12b444d2c4b7c0600acc35d21ae0","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-2026-49216","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:15:58.856Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-0cf1b4ad21c5be3a8b92259d29d2ee4e"],"technology":"symfony/ux-autocomplete","known_exclusions":[],"conditions_summary":"### Description\n\nThe Stimulus controller shipped with `symfony/ux-autocomplete` renders AJAX response items into the dropdown by interpolating the `text` field directly into HTML template literals (`${item[labelField]}`) inside `_createAutocompleteWithRemoteData()`. The value is parsed as HTML rather than text, so any markup contained in the AJAX response is executed by the browser.\n\nWhen the dropdown values are derived from user-supplied content, an attacker can craft a string that triggers stored XSS in the browser of any other user who later opens a page containing an autocomplete widget backed by the same data.\n\n### Resolution\n\nThe `option` and `item` renderers used in `_createAutocompleteWithRemoteData()` now use TomSelect's `escape` helper to HTML-escape the value by default. Endpoints that legitimately return HTML (for example, to highlight the search term) can opt back in to the previous behavior by setting `options_as_html: true`. The `AutocompleteChoiceTypeExtension` normalizer that previously forced `options_as_html=false` when `autocomplete_url` was set has been dropped so the opt-in is reachable from the form layer.\n\nThe patch for this issue is available [he","public_affected_ranges":[">= 2.2.0, < 2.36.0"]},{"certainty":"source_listed","source_ids":["sr-0cf1b4ad21c5be3a8b92259d29d2ee4e"],"technology":"symfony/ux-autocomplete","known_exclusions":[],"conditions_summary":"### Description\n\nThe Stimulus controller shipped with `symfony/ux-autocomplete` renders AJAX response items into the dropdown by interpolating the `text` field directly into HTML template literals (`${item[labelField]}`) inside `_createAutocompleteWithRemoteData()`. The value is parsed as HTML rather than text, so any markup contained in the AJAX response is executed by the browser.\n\nWhen the dropdown values are derived from user-supplied content, an attacker can craft a string that triggers stored XSS in the browser of any other user who later opens a page containing an autocomplete widget backed by the same data.\n\n### Resolution\n\nThe `option` and `item` renderers used in `_createAutocompleteWithRemoteData()` now use TomSelect's `escape` helper to HTML-escape the value by default. Endpoints that legitimately return HTML (for example, to highlight the search term) can opt back in to the previous behavior by setting `options_as_html: true`. The `AutocompleteChoiceTypeExtension` normalizer that previously forced `options_as_html=false` when `autocomplete_url` was set has been dropped so the opt-in is reachable from the form layer.\n\nThe patch for this issue is available [he","public_affected_ranges":[">= 3.0.0, < 3.1.0"]},{"certainty":"source_listed","source_ids":["sr-f21c8a2ad9220aa6be0359e058268dc6"],"technology":"symfony/ux-autocomplete","known_exclusions":[],"conditions_summary":"### Description\n\nThe Stimulus controller shipped with `symfony/ux-autocomplete` renders AJAX response items into the dropdown by interpolating the `text` field directly into HTML template literals (`${item[labelField]}`) inside `_createAutocompleteWithRemoteData()`. The value is parsed as HTML rather than text, so any markup contained in the AJAX response is executed by the browser.\n\nWhen the dropdown values are derived from user-supplied content, an attacker can craft a string that triggers stored XSS in the browser of any other user who later opens a page containing an autocomplete widget backed by the same data.\n\n### Resolution\n\nThe `option` and `item` renderers used in `_createAutocompleteWithRemoteData()` now use TomSelect's `escape` helper to HTML-escape the value by default. Endpoints that legitimately return HTML (for example, to highlight the search term) can opt back in to the previous behavior by setting `options_as_html: true`. The `AutocompleteChoiceTypeExtension` normalizer that previously forced `options_as_html=false` when `autocomplete_url` was set has been dropped so the opt-in is reachable from the form layer.\n\nThe patch for this issue is available [he","public_affected_ranges":["ECOSYSTEM: introduced 2.2.0; fixed 2.36.0"]},{"certainty":"source_listed","source_ids":["sr-f21c8a2ad9220aa6be0359e058268dc6"],"technology":"symfony/ux-autocomplete","known_exclusions":[],"conditions_summary":"### Description\n\nThe Stimulus controller shipped with `symfony/ux-autocomplete` renders AJAX response items into the dropdown by interpolating the `text` field directly into HTML template literals (`${item[labelField]}`) inside `_createAutocompleteWithRemoteData()`. The value is parsed as HTML rather than text, so any markup contained in the AJAX response is executed by the browser.\n\nWhen the dropdown values are derived from user-supplied content, an attacker can craft a string that triggers stored XSS in the browser of any other user who later opens a page containing an autocomplete widget backed by the same data.\n\n### Resolution\n\nThe `option` and `item` renderers used in `_createAutocompleteWithRemoteData()` now use TomSelect's `escape` helper to HTML-escape the value by default. Endpoints that legitimately return HTML (for example, to highlight the search term) can opt back in to the previous behavior by setting `options_as_html: true`. The `AutocompleteChoiceTypeExtension` normalizer that previously forced `options_as_html=false` when `autocomplete_url` was set has been dropped so the opt-in is reachable from the form layer.\n\nThe patch for this issue is available [he","public_affected_ranges":["ECOSYSTEM: introduced 3.0.0; fixed 3.1.0"]}],"null_published_at":"2026-11-07T14:01:58.738Z","source_updated_at":"2026-06-19T19:35:06.000Z","source_disclosed_at":"2026-06-19T19:35:05.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.984Z"},{"id":"NVI-00008010","kind":"vulnerability","title":"symfony/ux-autocomplete: XSS via unescaped AJAX response data","revision":4,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-mwqm-4fw3-cjvr","CVE-2026-49216"],"plain_summary":"GitHub lists this reviewed advisory for symfony/ux-autocomplete, symfony/ux-autocomplete. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-5558acdeec2c415a8d2fcdcbecaa908a"],"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},{"summary":"The original advisory lists fixed boundaries 2.36.0 for symfony/ux-autocomplete. Confirm the publisher’s latest guidance.","source_ids":["sr-f21c8a2ad9220aa6be0359e058268dc6"],"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 3.1.0 for symfony/ux-autocomplete. Confirm the publisher’s latest guidance.","source_ids":["sr-f21c8a2ad9220aa6be0359e058268dc6"],"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":[{"kind":"CVSS","as_of":"2026-10-24T20:10:00.137Z","value":"5.4 MEDIUM (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-34aef7ced2890aa096b3fb53f0527e3c"},{"kind":"CVSS","as_of":"2026-10-24T20:10:00.137Z","value":"5.1 MEDIUM (4.0)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-34aef7ced2890aa096b3fb53f0527e3c"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.312%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.24073. Missing scores are unknown.","source_id":"sr-5558acdeec2c415a8d2fcdcbecaa908a"}],"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-0cf1b4ad21c5be3a8b92259d29d2ee4e","url":"https://github.com/advisories/GHSA-mwqm-4fw3-cjvr","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-mwqm-4fw3-cjvr","publisher":"GitHub Advisory Database","observed_at":"2026-11-06T07:19:16.585Z"},{"id":"sr-f21c8a2ad9220aa6be0359e058268dc6","url":"https://github.com/advisories/GHSA-mwqm-4fw3-cjvr","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-mwqm-4fw3-cjvr","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.984Z"},{"id":"sr-34aef7ced2890aa096b3fb53f0527e3c","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-49216","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-49216","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-03T22:35:35.055Z"},{"id":"sr-5558acdeec2c415a8d2fcdcbecaa908a","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-2026-49216","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.382Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-0cf1b4ad21c5be3a8b92259d29d2ee4e"],"technology":"symfony/ux-autocomplete","known_exclusions":[],"conditions_summary":"### Description\n\nThe Stimulus controller shipped with `symfony/ux-autocomplete` renders AJAX response items into the dropdown by interpolating the `text` field directly into HTML template literals (`${item[labelField]}`) inside `_createAutocompleteWithRemoteData()`. The value is parsed as HTML rather than text, so any markup contained in the AJAX response is executed by the browser.\n\nWhen the dropdown values are derived from user-supplied content, an attacker can craft a string that triggers stored XSS in the browser of any other user who later opens a page containing an autocomplete widget backed by the same data.\n\n### Resolution\n\nThe `option` and `item` renderers used in `_createAutocompleteWithRemoteData()` now use TomSelect's `escape` helper to HTML-escape the value by default. Endpoints that legitimately return HTML (for example, to highlight the search term) can opt back in to the previous behavior by setting `options_as_html: true`. The `AutocompleteChoiceTypeExtension` normalizer that previously forced `options_as_html=false` when `autocomplete_url` was set has been dropped so the opt-in is reachable from the form layer.\n\nThe patch for this issue is available [he","public_affected_ranges":[">= 2.2.0, < 2.36.0"]},{"certainty":"source_listed","source_ids":["sr-0cf1b4ad21c5be3a8b92259d29d2ee4e"],"technology":"symfony/ux-autocomplete","known_exclusions":[],"conditions_summary":"### Description\n\nThe Stimulus controller shipped with `symfony/ux-autocomplete` renders AJAX response items into the dropdown by interpolating the `text` field directly into HTML template literals (`${item[labelField]}`) inside `_createAutocompleteWithRemoteData()`. The value is parsed as HTML rather than text, so any markup contained in the AJAX response is executed by the browser.\n\nWhen the dropdown values are derived from user-supplied content, an attacker can craft a string that triggers stored XSS in the browser of any other user who later opens a page containing an autocomplete widget backed by the same data.\n\n### Resolution\n\nThe `option` and `item` renderers used in `_createAutocompleteWithRemoteData()` now use TomSelect's `escape` helper to HTML-escape the value by default. Endpoints that legitimately return HTML (for example, to highlight the search term) can opt back in to the previous behavior by setting `options_as_html: true`. The `AutocompleteChoiceTypeExtension` normalizer that previously forced `options_as_html=false` when `autocomplete_url` was set has been dropped so the opt-in is reachable from the form layer.\n\nThe patch for this issue is available [he","public_affected_ranges":[">= 3.0.0, < 3.1.0"]},{"certainty":"source_listed","source_ids":["sr-f21c8a2ad9220aa6be0359e058268dc6"],"technology":"symfony/ux-autocomplete","known_exclusions":[],"conditions_summary":"### Description\n\nThe Stimulus controller shipped with `symfony/ux-autocomplete` renders AJAX response items into the dropdown by interpolating the `text` field directly into HTML template literals (`${item[labelField]}`) inside `_createAutocompleteWithRemoteData()`. The value is parsed as HTML rather than text, so any markup contained in the AJAX response is executed by the browser.\n\nWhen the dropdown values are derived from user-supplied content, an attacker can craft a string that triggers stored XSS in the browser of any other user who later opens a page containing an autocomplete widget backed by the same data.\n\n### Resolution\n\nThe `option` and `item` renderers used in `_createAutocompleteWithRemoteData()` now use TomSelect's `escape` helper to HTML-escape the value by default. Endpoints that legitimately return HTML (for example, to highlight the search term) can opt back in to the previous behavior by setting `options_as_html: true`. The `AutocompleteChoiceTypeExtension` normalizer that previously forced `options_as_html=false` when `autocomplete_url` was set has been dropped so the opt-in is reachable from the form layer.\n\nThe patch for this issue is available [he","public_affected_ranges":["ECOSYSTEM: introduced 2.2.0; fixed 2.36.0"]},{"certainty":"source_listed","source_ids":["sr-f21c8a2ad9220aa6be0359e058268dc6"],"technology":"symfony/ux-autocomplete","known_exclusions":[],"conditions_summary":"### Description\n\nThe Stimulus controller shipped with `symfony/ux-autocomplete` renders AJAX response items into the dropdown by interpolating the `text` field directly into HTML template literals (`${item[labelField]}`) inside `_createAutocompleteWithRemoteData()`. The value is parsed as HTML rather than text, so any markup contained in the AJAX response is executed by the browser.\n\nWhen the dropdown values are derived from user-supplied content, an attacker can craft a string that triggers stored XSS in the browser of any other user who later opens a page containing an autocomplete widget backed by the same data.\n\n### Resolution\n\nThe `option` and `item` renderers used in `_createAutocompleteWithRemoteData()` now use TomSelect's `escape` helper to HTML-escape the value by default. Endpoints that legitimately return HTML (for example, to highlight the search term) can opt back in to the previous behavior by setting `options_as_html: true`. The `AutocompleteChoiceTypeExtension` normalizer that previously forced `options_as_html=false` when `autocomplete_url` was set has been dropped so the opt-in is reachable from the form layer.\n\nThe patch for this issue is available [he","public_affected_ranges":["ECOSYSTEM: introduced 3.0.0; fixed 3.1.0"]}],"null_published_at":"2026-11-07T07:07:39.807Z","source_updated_at":"2026-06-19T19:35:06.000Z","source_disclosed_at":"2026-06-19T19:35:05.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:42:30.984Z"},{"id":"NVI-00008010","kind":"vulnerability","title":"symfony/ux-autocomplete: XSS via unescaped AJAX response data","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-mwqm-4fw3-cjvr","CVE-2026-49216"],"plain_summary":"OSV carries this publisher advisory for symfony/ux-autocomplete, symfony/ux-autocomplete. 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 2.36.0 for symfony/ux-autocomplete. Confirm the publisher’s latest guidance.","source_ids":["sr-f21c8a2ad9220aa6be0359e058268dc6"],"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 3.1.0 for symfony/ux-autocomplete. Confirm the publisher’s latest guidance.","source_ids":["sr-f21c8a2ad9220aa6be0359e058268dc6"],"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-5558acdeec2c415a8d2fcdcbecaa908a"],"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":"CVSS","as_of":"2026-10-24T20:10:00.137Z","value":"5.4 MEDIUM (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-34aef7ced2890aa096b3fb53f0527e3c"},{"kind":"CVSS","as_of":"2026-10-24T20:10:00.137Z","value":"5.1 MEDIUM (4.0)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-34aef7ced2890aa096b3fb53f0527e3c"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.312%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.24073. Missing scores are unknown.","source_id":"sr-5558acdeec2c415a8d2fcdcbecaa908a"}],"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-f21c8a2ad9220aa6be0359e058268dc6","url":"https://github.com/advisories/GHSA-mwqm-4fw3-cjvr","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-mwqm-4fw3-cjvr","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.984Z"},{"id":"sr-34aef7ced2890aa096b3fb53f0527e3c","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-49216","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-49216","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-03T22:35:35.055Z"},{"id":"sr-5558acdeec2c415a8d2fcdcbecaa908a","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-2026-49216","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.382Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-f21c8a2ad9220aa6be0359e058268dc6"],"technology":"symfony/ux-autocomplete","known_exclusions":[],"conditions_summary":"### Description\n\nThe Stimulus controller shipped with `symfony/ux-autocomplete` renders AJAX response items into the dropdown by interpolating the `text` field directly into HTML template literals (`${item[labelField]}`) inside `_createAutocompleteWithRemoteData()`. The value is parsed as HTML rather than text, so any markup contained in the AJAX response is executed by the browser.\n\nWhen the dropdown values are derived from user-supplied content, an attacker can craft a string that triggers stored XSS in the browser of any other user who later opens a page containing an autocomplete widget backed by the same data.\n\n### Resolution\n\nThe `option` and `item` renderers used in `_createAutocompleteWithRemoteData()` now use TomSelect's `escape` helper to HTML-escape the value by default. Endpoints that legitimately return HTML (for example, to highlight the search term) can opt back in to the previous behavior by setting `options_as_html: true`. The `AutocompleteChoiceTypeExtension` normalizer that previously forced `options_as_html=false` when `autocomplete_url` was set has been dropped so the opt-in is reachable from the form layer.\n\nThe patch for this issue is available [he","public_affected_ranges":["ECOSYSTEM: introduced 2.2.0; fixed 2.36.0"]},{"certainty":"source_listed","source_ids":["sr-f21c8a2ad9220aa6be0359e058268dc6"],"technology":"symfony/ux-autocomplete","known_exclusions":[],"conditions_summary":"### Description\n\nThe Stimulus controller shipped with `symfony/ux-autocomplete` renders AJAX response items into the dropdown by interpolating the `text` field directly into HTML template literals (`${item[labelField]}`) inside `_createAutocompleteWithRemoteData()`. The value is parsed as HTML rather than text, so any markup contained in the AJAX response is executed by the browser.\n\nWhen the dropdown values are derived from user-supplied content, an attacker can craft a string that triggers stored XSS in the browser of any other user who later opens a page containing an autocomplete widget backed by the same data.\n\n### Resolution\n\nThe `option` and `item` renderers used in `_createAutocompleteWithRemoteData()` now use TomSelect's `escape` helper to HTML-escape the value by default. Endpoints that legitimately return HTML (for example, to highlight the search term) can opt back in to the previous behavior by setting `options_as_html: true`. The `AutocompleteChoiceTypeExtension` normalizer that previously forced `options_as_html=false` when `autocomplete_url` was set has been dropped so the opt-in is reachable from the form layer.\n\nThe patch for this issue is available [he","public_affected_ranges":["ECOSYSTEM: introduced 3.0.0; fixed 3.1.0"]}],"null_published_at":"2026-11-04T10:04:35.930Z","source_updated_at":"2026-09-10T03:51:09.172Z","source_disclosed_at":"2026-06-19T19:35:05.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:42:30.984Z"},{"id":"NVI-00008010","kind":"vulnerability","title":"symfony/ux-autocomplete: XSS via unescaped AJAX response data","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-mwqm-4fw3-cjvr","CVE-2026-49216"],"plain_summary":"OSV carries this publisher advisory for symfony/ux-autocomplete, symfony/ux-autocomplete. 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 2.36.0 for symfony/ux-autocomplete. Confirm the publisher’s latest guidance.","source_ids":["sr-f21c8a2ad9220aa6be0359e058268dc6"],"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 3.1.0 for symfony/ux-autocomplete. Confirm the publisher’s latest guidance.","source_ids":["sr-f21c8a2ad9220aa6be0359e058268dc6"],"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-5558acdeec2c415a8d2fcdcbecaa908a"],"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-10-31T12:00:27.000Z","value":"0.312%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.24073. Missing scores are unknown.","source_id":"sr-5558acdeec2c415a8d2fcdcbecaa908a"}],"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-f21c8a2ad9220aa6be0359e058268dc6","url":"https://github.com/advisories/GHSA-mwqm-4fw3-cjvr","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-mwqm-4fw3-cjvr","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.984Z"},{"id":"sr-5558acdeec2c415a8d2fcdcbecaa908a","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-2026-49216","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.382Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-f21c8a2ad9220aa6be0359e058268dc6"],"technology":"symfony/ux-autocomplete","known_exclusions":[],"conditions_summary":"### Description\n\nThe Stimulus controller shipped with `symfony/ux-autocomplete` renders AJAX response items into the dropdown by interpolating the `text` field directly into HTML template literals (`${item[labelField]}`) inside `_createAutocompleteWithRemoteData()`. The value is parsed as HTML rather than text, so any markup contained in the AJAX response is executed by the browser.\n\nWhen the dropdown values are derived from user-supplied content, an attacker can craft a string that triggers stored XSS in the browser of any other user who later opens a page containing an autocomplete widget backed by the same data.\n\n### Resolution\n\nThe `option` and `item` renderers used in `_createAutocompleteWithRemoteData()` now use TomSelect's `escape` helper to HTML-escape the value by default. Endpoints that legitimately return HTML (for example, to highlight the search term) can opt back in to the previous behavior by setting `options_as_html: true`. The `AutocompleteChoiceTypeExtension` normalizer that previously forced `options_as_html=false` when `autocomplete_url` was set has been dropped so the opt-in is reachable from the form layer.\n\nThe patch for this issue is available [he","public_affected_ranges":["ECOSYSTEM: introduced 2.2.0; fixed 2.36.0"]},{"certainty":"source_listed","source_ids":["sr-f21c8a2ad9220aa6be0359e058268dc6"],"technology":"symfony/ux-autocomplete","known_exclusions":[],"conditions_summary":"### Description\n\nThe Stimulus controller shipped with `symfony/ux-autocomplete` renders AJAX response items into the dropdown by interpolating the `text` field directly into HTML template literals (`${item[labelField]}`) inside `_createAutocompleteWithRemoteData()`. The value is parsed as HTML rather than text, so any markup contained in the AJAX response is executed by the browser.\n\nWhen the dropdown values are derived from user-supplied content, an attacker can craft a string that triggers stored XSS in the browser of any other user who later opens a page containing an autocomplete widget backed by the same data.\n\n### Resolution\n\nThe `option` and `item` renderers used in `_createAutocompleteWithRemoteData()` now use TomSelect's `escape` helper to HTML-escape the value by default. Endpoints that legitimately return HTML (for example, to highlight the search term) can opt back in to the previous behavior by setting `options_as_html: true`. The `AutocompleteChoiceTypeExtension` normalizer that previously forced `options_as_html=false` when `autocomplete_url` was set has been dropped so the opt-in is reachable from the form layer.\n\nThe patch for this issue is available [he","public_affected_ranges":["ECOSYSTEM: introduced 3.0.0; fixed 3.1.0"]}],"null_published_at":"2026-11-01T01:04:04.846Z","source_updated_at":"2026-09-10T03:51:09.172Z","source_disclosed_at":"2026-06-19T19:35:05.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.984Z"},{"id":"NVI-00008010","kind":"vulnerability","title":"symfony/ux-autocomplete: XSS via unescaped AJAX response data","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-mwqm-4fw3-cjvr","CVE-2026-49216"],"plain_summary":"OSV carries this publisher advisory for symfony/ux-autocomplete, symfony/ux-autocomplete. 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 2.36.0 for symfony/ux-autocomplete. Confirm the publisher’s latest guidance.","source_ids":["sr-f21c8a2ad9220aa6be0359e058268dc6"],"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 3.1.0 for symfony/ux-autocomplete. Confirm the publisher’s latest guidance.","source_ids":["sr-f21c8a2ad9220aa6be0359e058268dc6"],"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-f21c8a2ad9220aa6be0359e058268dc6","url":"https://github.com/advisories/GHSA-mwqm-4fw3-cjvr","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-mwqm-4fw3-cjvr","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.984Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-f21c8a2ad9220aa6be0359e058268dc6"],"technology":"symfony/ux-autocomplete","known_exclusions":[],"conditions_summary":"### Description\n\nThe Stimulus controller shipped with `symfony/ux-autocomplete` renders AJAX response items into the dropdown by interpolating the `text` field directly into HTML template literals (`${item[labelField]}`) inside `_createAutocompleteWithRemoteData()`. The value is parsed as HTML rather than text, so any markup contained in the AJAX response is executed by the browser.\n\nWhen the dropdown values are derived from user-supplied content, an attacker can craft a string that triggers stored XSS in the browser of any other user who later opens a page containing an autocomplete widget backed by the same data.\n\n### Resolution\n\nThe `option` and `item` renderers used in `_createAutocompleteWithRemoteData()` now use TomSelect's `escape` helper to HTML-escape the value by default. Endpoints that legitimately return HTML (for example, to highlight the search term) can opt back in to the previous behavior by setting `options_as_html: true`. The `AutocompleteChoiceTypeExtension` normalizer that previously forced `options_as_html=false` when `autocomplete_url` was set has been dropped so the opt-in is reachable from the form layer.\n\nThe patch for this issue is available [he","public_affected_ranges":["ECOSYSTEM: introduced 2.2.0; fixed 2.36.0"]},{"certainty":"source_listed","source_ids":["sr-f21c8a2ad9220aa6be0359e058268dc6"],"technology":"symfony/ux-autocomplete","known_exclusions":[],"conditions_summary":"### Description\n\nThe Stimulus controller shipped with `symfony/ux-autocomplete` renders AJAX response items into the dropdown by interpolating the `text` field directly into HTML template literals (`${item[labelField]}`) inside `_createAutocompleteWithRemoteData()`. The value is parsed as HTML rather than text, so any markup contained in the AJAX response is executed by the browser.\n\nWhen the dropdown values are derived from user-supplied content, an attacker can craft a string that triggers stored XSS in the browser of any other user who later opens a page containing an autocomplete widget backed by the same data.\n\n### Resolution\n\nThe `option` and `item` renderers used in `_createAutocompleteWithRemoteData()` now use TomSelect's `escape` helper to HTML-escape the value by default. Endpoints that legitimately return HTML (for example, to highlight the search term) can opt back in to the previous behavior by setting `options_as_html: true`. The `AutocompleteChoiceTypeExtension` normalizer that previously forced `options_as_html=false` when `autocomplete_url` was set has been dropped so the opt-in is reachable from the form layer.\n\nThe patch for this issue is available [he","public_affected_ranges":["ECOSYSTEM: introduced 3.0.0; fixed 3.1.0"]}],"null_published_at":"2026-10-31T22:13:22.825Z","source_updated_at":"2026-09-10T03:51:09.172Z","source_disclosed_at":"2026-06-19T19:35:05.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.984Z"}],"next_cursor":null,"snapshot_revision":"42594"}