{"items":[{"id":"NVI-00010752","kind":"vulnerability","title":"vite: `server.fs.deny` bypass on Windows alternate paths","revision":4,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-fx2h-pf6j-xcff","CVE-2026-53571"],"plain_summary":"GitHub lists this reviewed advisory for vite, vite, vite, vite-plus. 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-04082320fde85923107e8bc6f86b779c"],"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 8.0.16 for vite. Confirm the publisher’s latest guidance.","source_ids":["sr-9b1f3b69d571bf9c241f09c5a87d5d10"],"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 7.3.5 for vite. Confirm the publisher’s latest guidance.","source_ids":["sr-9b1f3b69d571bf9c241f09c5a87d5d10"],"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 6.4.3 for vite. Confirm the publisher’s latest guidance.","source_ids":["sr-9b1f3b69d571bf9c241f09c5a87d5d10"],"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 0.1.24 for vite-plus. Confirm the publisher’s latest guidance.","source_ids":["sr-9b1f3b69d571bf9c241f09c5a87d5d10"],"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":"EPSS","as_of":"2026-11-05T12:03:04.000Z","value":"0.577%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.47675. Missing scores are unknown.","source_id":"sr-04082320fde85923107e8bc6f86b779c"}],"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-e85cc236fa954d073c06cb89e7a62dd4","url":"https://github.com/advisories/GHSA-fx2h-pf6j-xcff","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-fx2h-pf6j-xcff","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T22:06:46.371Z"},{"id":"sr-9b1f3b69d571bf9c241f09c5a87d5d10","url":"https://github.com/advisories/GHSA-fx2h-pf6j-xcff","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-fx2h-pf6j-xcff","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-11-03T09:58:55.136Z"},{"id":"sr-04082320fde85923107e8bc6f86b779c","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-53571","publisher":"FIRST EPSS","observed_at":"2026-11-06T07:17:46.382Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-e85cc236fa954d073c06cb89e7a62dd4"],"technology":"vite","known_exclusions":[],"conditions_summary":"### Summary\n\nThe contents of files that are specified by `server.fs.deny` can be returned to the browser on Windows.\n\n### Impact\n\nOnly apps that match the following conditions are affected:\n\n- explicitly exposes the Vite dev server to the network (using `--host` or `server.host` config option)\n- the sensitive file exists in the allowed directories specified by `server.fs.allow`\n- either of:\n  - the sensitive file exists in an NTFS volume\n  - the dev server is running on Windows and the sensitive file exists in a volume that 8.3 short name generation is enabled (it is enabled by default on system volumes)\n\n### Details\n\nVite’s dev server denies direct access to sensitive files through `server.fs.deny`, including entries such as `.env`, `.env.*`, and `*.{crt,pem}`. However, on Windows, the deny logic does not correctly normalize NTFS ADS path forms before access checks are applied.\nBecause of this, requests such as `/.env::$DATA?raw` are treated as allowed paths, while Windows resolves them to the original file'","public_affected_ranges":[">= 8.0.0, <= 8.0.15"]},{"certainty":"source_listed","source_ids":["sr-e85cc236fa954d073c06cb89e7a62dd4"],"technology":"vite","known_exclusions":[],"conditions_summary":"### Summary\n\nThe contents of files that are specified by `server.fs.deny` can be returned to the browser on Windows.\n\n### Impact\n\nOnly apps that match the following conditions are affected:\n\n- explicitly exposes the Vite dev server to the network (using `--host` or `server.host` config option)\n- the sensitive file exists in the allowed directories specified by `server.fs.allow`\n- either of:\n  - the sensitive file exists in an NTFS volume\n  - the dev server is running on Windows and the sensitive file exists in a volume that 8.3 short name generation is enabled (it is enabled by default on system volumes)\n\n### Details\n\nVite’s dev server denies direct access to sensitive files through `server.fs.deny`, including entries such as `.env`, `.env.*`, and `*.{crt,pem}`. However, on Windows, the deny logic does not correctly normalize NTFS ADS path forms before access checks are applied.\nBecause of this, requests such as `/.env::$DATA?raw` are treated as allowed paths, while Windows resolves them to the original file'","public_affected_ranges":[">= 7.0.0, <= 7.3.4"]},{"certainty":"source_listed","source_ids":["sr-e85cc236fa954d073c06cb89e7a62dd4"],"technology":"vite","known_exclusions":[],"conditions_summary":"### Summary\n\nThe contents of files that are specified by `server.fs.deny` can be returned to the browser on Windows.\n\n### Impact\n\nOnly apps that match the following conditions are affected:\n\n- explicitly exposes the Vite dev server to the network (using `--host` or `server.host` config option)\n- the sensitive file exists in the allowed directories specified by `server.fs.allow`\n- either of:\n  - the sensitive file exists in an NTFS volume\n  - the dev server is running on Windows and the sensitive file exists in a volume that 8.3 short name generation is enabled (it is enabled by default on system volumes)\n\n### Details\n\nVite’s dev server denies direct access to sensitive files through `server.fs.deny`, including entries such as `.env`, `.env.*`, and `*.{crt,pem}`. However, on Windows, the deny logic does not correctly normalize NTFS ADS path forms before access checks are applied.\nBecause of this, requests such as `/.env::$DATA?raw` are treated as allowed paths, while Windows resolves them to the original file'","public_affected_ranges":["<= 6.4.2"]},{"certainty":"source_listed","source_ids":["sr-e85cc236fa954d073c06cb89e7a62dd4"],"technology":"vite-plus","known_exclusions":[],"conditions_summary":"### Summary\n\nThe contents of files that are specified by `server.fs.deny` can be returned to the browser on Windows.\n\n### Impact\n\nOnly apps that match the following conditions are affected:\n\n- explicitly exposes the Vite dev server to the network (using `--host` or `server.host` config option)\n- the sensitive file exists in the allowed directories specified by `server.fs.allow`\n- either of:\n  - the sensitive file exists in an NTFS volume\n  - the dev server is running on Windows and the sensitive file exists in a volume that 8.3 short name generation is enabled (it is enabled by default on system volumes)\n\n### Details\n\nVite’s dev server denies direct access to sensitive files through `server.fs.deny`, including entries such as `.env`, `.env.*`, and `*.{crt,pem}`. However, on Windows, the deny logic does not correctly normalize NTFS ADS path forms before access checks are applied.\nBecause of this, requests such as `/.env::$DATA?raw` are treated as allowed paths, while Windows resolves them to the original file'","public_affected_ranges":["<= 0.1.23"]},{"certainty":"source_listed","source_ids":["sr-9b1f3b69d571bf9c241f09c5a87d5d10"],"technology":"vite","known_exclusions":[],"conditions_summary":"### Summary\n\nThe contents of files that are specified by `server.fs.deny` can be returned to the browser on Windows.\n\n### Impact\n\nOnly apps that match the following conditions are affected:\n\n- explicitly exposes the Vite dev server to the network (using `--host` or `server.host` config option)\n- the sensitive file exists in the allowed directories specified by `server.fs.allow`\n- either of:\n  - the sensitive file exists in an NTFS volume\n  - the dev server is running on Windows and the sensitive file exists in a volume that 8.3 short name generation is enabled (it is enabled by default on system volumes)\n\n### Details\n\nVite’s dev server denies direct access to sensitive files through `server.fs.deny`, including entries such as `.env`, `.env.*`, and `*.{crt,pem}`. However, on Windows, the deny logic does not correctly normalize NTFS ADS path forms before access checks are applied.\nBecause of this, requests such as `/.env::$DATA?raw` are treated as allowed paths, while Windows resolves them to the original file'","public_affected_ranges":["SEMVER: introduced 8.0.0; fixed 8.0.16"]},{"certainty":"source_listed","source_ids":["sr-9b1f3b69d571bf9c241f09c5a87d5d10"],"technology":"vite","known_exclusions":[],"conditions_summary":"### Summary\n\nThe contents of files that are specified by `server.fs.deny` can be returned to the browser on Windows.\n\n### Impact\n\nOnly apps that match the following conditions are affected:\n\n- explicitly exposes the Vite dev server to the network (using `--host` or `server.host` config option)\n- the sensitive file exists in the allowed directories specified by `server.fs.allow`\n- either of:\n  - the sensitive file exists in an NTFS volume\n  - the dev server is running on Windows and the sensitive file exists in a volume that 8.3 short name generation is enabled (it is enabled by default on system volumes)\n\n### Details\n\nVite’s dev server denies direct access to sensitive files through `server.fs.deny`, including entries such as `.env`, `.env.*`, and `*.{crt,pem}`. However, on Windows, the deny logic does not correctly normalize NTFS ADS path forms before access checks are applied.\nBecause of this, requests such as `/.env::$DATA?raw` are treated as allowed paths, while Windows resolves them to the original file'","public_affected_ranges":["SEMVER: introduced 7.0.0; fixed 7.3.5"]},{"certainty":"source_listed","source_ids":["sr-9b1f3b69d571bf9c241f09c5a87d5d10"],"technology":"vite","known_exclusions":[],"conditions_summary":"### Summary\n\nThe contents of files that are specified by `server.fs.deny` can be returned to the browser on Windows.\n\n### Impact\n\nOnly apps that match the following conditions are affected:\n\n- explicitly exposes the Vite dev server to the network (using `--host` or `server.host` config option)\n- the sensitive file exists in the allowed directories specified by `server.fs.allow`\n- either of:\n  - the sensitive file exists in an NTFS volume\n  - the dev server is running on Windows and the sensitive file exists in a volume that 8.3 short name generation is enabled (it is enabled by default on system volumes)\n\n### Details\n\nVite’s dev server denies direct access to sensitive files through `server.fs.deny`, including entries such as `.env`, `.env.*`, and `*.{crt,pem}`. However, on Windows, the deny logic does not correctly normalize NTFS ADS path forms before access checks are applied.\nBecause of this, requests such as `/.env::$DATA?raw` are treated as allowed paths, while Windows resolves them to the original file'","public_affected_ranges":["SEMVER: introduced 0; fixed 6.4.3"]},{"certainty":"source_listed","source_ids":["sr-9b1f3b69d571bf9c241f09c5a87d5d10"],"technology":"vite-plus","known_exclusions":[],"conditions_summary":"### Summary\n\nThe contents of files that are specified by `server.fs.deny` can be returned to the browser on Windows.\n\n### Impact\n\nOnly apps that match the following conditions are affected:\n\n- explicitly exposes the Vite dev server to the network (using `--host` or `server.host` config option)\n- the sensitive file exists in the allowed directories specified by `server.fs.allow`\n- either of:\n  - the sensitive file exists in an NTFS volume\n  - the dev server is running on Windows and the sensitive file exists in a volume that 8.3 short name generation is enabled (it is enabled by default on system volumes)\n\n### Details\n\nVite’s dev server denies direct access to sensitive files through `server.fs.deny`, including entries such as `.env`, `.env.*`, and `*.{crt,pem}`. However, on Windows, the deny logic does not correctly normalize NTFS ADS path forms before access checks are applied.\nBecause of this, requests such as `/.env::$DATA?raw` are treated as allowed paths, while Windows resolves them to the original file'","public_affected_ranges":["SEMVER: introduced 0; fixed 0.1.24"]}],"null_published_at":"2026-11-07T07:07:42.546Z","source_updated_at":"2026-10-27T14:58:31.000Z","source_disclosed_at":"2026-06-15T17:17:45.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-31T22:06:46.371Z"},{"id":"NVI-00010752","kind":"vulnerability","title":"vite: `server.fs.deny` bypass on Windows alternate paths","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-fx2h-pf6j-xcff","CVE-2026-53571"],"plain_summary":"GitHub lists this reviewed advisory for vite, vite, vite, vite-plus. 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-0680a6625510e0d4d85d9167d59eceac"],"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 8.0.16 for vite. Confirm the publisher’s latest guidance.","source_ids":["sr-9b1f3b69d571bf9c241f09c5a87d5d10"],"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 7.3.5 for vite. Confirm the publisher’s latest guidance.","source_ids":["sr-9b1f3b69d571bf9c241f09c5a87d5d10"],"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 6.4.3 for vite. Confirm the publisher’s latest guidance.","source_ids":["sr-9b1f3b69d571bf9c241f09c5a87d5d10"],"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 0.1.24 for vite-plus. Confirm the publisher’s latest guidance.","source_ids":["sr-9b1f3b69d571bf9c241f09c5a87d5d10"],"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":"EPSS","as_of":"2026-11-02T12:00:30.000Z","value":"0.577%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.47528. Missing scores are unknown.","source_id":"sr-0680a6625510e0d4d85d9167d59eceac"}],"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-e85cc236fa954d073c06cb89e7a62dd4","url":"https://github.com/advisories/GHSA-fx2h-pf6j-xcff","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-fx2h-pf6j-xcff","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T22:06:46.371Z"},{"id":"sr-9b1f3b69d571bf9c241f09c5a87d5d10","url":"https://github.com/advisories/GHSA-fx2h-pf6j-xcff","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-fx2h-pf6j-xcff","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-11-03T09:58:55.136Z"},{"id":"sr-0680a6625510e0d4d85d9167d59eceac","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-53571","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:15:58.856Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-e85cc236fa954d073c06cb89e7a62dd4"],"technology":"vite","known_exclusions":[],"conditions_summary":"### Summary\n\nThe contents of files that are specified by `server.fs.deny` can be returned to the browser on Windows.\n\n### Impact\n\nOnly apps that match the following conditions are affected:\n\n- explicitly exposes the Vite dev server to the network (using `--host` or `server.host` config option)\n- the sensitive file exists in the allowed directories specified by `server.fs.allow`\n- either of:\n  - the sensitive file exists in an NTFS volume\n  - the dev server is running on Windows and the sensitive file exists in a volume that 8.3 short name generation is enabled (it is enabled by default on system volumes)\n\n### Details\n\nVite’s dev server denies direct access to sensitive files through `server.fs.deny`, including entries such as `.env`, `.env.*`, and `*.{crt,pem}`. However, on Windows, the deny logic does not correctly normalize NTFS ADS path forms before access checks are applied.\nBecause of this, requests such as `/.env::$DATA?raw` are treated as allowed paths, while Windows resolves them to the original file'","public_affected_ranges":[">= 8.0.0, <= 8.0.15"]},{"certainty":"source_listed","source_ids":["sr-e85cc236fa954d073c06cb89e7a62dd4"],"technology":"vite","known_exclusions":[],"conditions_summary":"### Summary\n\nThe contents of files that are specified by `server.fs.deny` can be returned to the browser on Windows.\n\n### Impact\n\nOnly apps that match the following conditions are affected:\n\n- explicitly exposes the Vite dev server to the network (using `--host` or `server.host` config option)\n- the sensitive file exists in the allowed directories specified by `server.fs.allow`\n- either of:\n  - the sensitive file exists in an NTFS volume\n  - the dev server is running on Windows and the sensitive file exists in a volume that 8.3 short name generation is enabled (it is enabled by default on system volumes)\n\n### Details\n\nVite’s dev server denies direct access to sensitive files through `server.fs.deny`, including entries such as `.env`, `.env.*`, and `*.{crt,pem}`. However, on Windows, the deny logic does not correctly normalize NTFS ADS path forms before access checks are applied.\nBecause of this, requests such as `/.env::$DATA?raw` are treated as allowed paths, while Windows resolves them to the original file'","public_affected_ranges":[">= 7.0.0, <= 7.3.4"]},{"certainty":"source_listed","source_ids":["sr-e85cc236fa954d073c06cb89e7a62dd4"],"technology":"vite","known_exclusions":[],"conditions_summary":"### Summary\n\nThe contents of files that are specified by `server.fs.deny` can be returned to the browser on Windows.\n\n### Impact\n\nOnly apps that match the following conditions are affected:\n\n- explicitly exposes the Vite dev server to the network (using `--host` or `server.host` config option)\n- the sensitive file exists in the allowed directories specified by `server.fs.allow`\n- either of:\n  - the sensitive file exists in an NTFS volume\n  - the dev server is running on Windows and the sensitive file exists in a volume that 8.3 short name generation is enabled (it is enabled by default on system volumes)\n\n### Details\n\nVite’s dev server denies direct access to sensitive files through `server.fs.deny`, including entries such as `.env`, `.env.*`, and `*.{crt,pem}`. However, on Windows, the deny logic does not correctly normalize NTFS ADS path forms before access checks are applied.\nBecause of this, requests such as `/.env::$DATA?raw` are treated as allowed paths, while Windows resolves them to the original file'","public_affected_ranges":["<= 6.4.2"]},{"certainty":"source_listed","source_ids":["sr-e85cc236fa954d073c06cb89e7a62dd4"],"technology":"vite-plus","known_exclusions":[],"conditions_summary":"### Summary\n\nThe contents of files that are specified by `server.fs.deny` can be returned to the browser on Windows.\n\n### Impact\n\nOnly apps that match the following conditions are affected:\n\n- explicitly exposes the Vite dev server to the network (using `--host` or `server.host` config option)\n- the sensitive file exists in the allowed directories specified by `server.fs.allow`\n- either of:\n  - the sensitive file exists in an NTFS volume\n  - the dev server is running on Windows and the sensitive file exists in a volume that 8.3 short name generation is enabled (it is enabled by default on system volumes)\n\n### Details\n\nVite’s dev server denies direct access to sensitive files through `server.fs.deny`, including entries such as `.env`, `.env.*`, and `*.{crt,pem}`. However, on Windows, the deny logic does not correctly normalize NTFS ADS path forms before access checks are applied.\nBecause of this, requests such as `/.env::$DATA?raw` are treated as allowed paths, while Windows resolves them to the original file'","public_affected_ranges":["<= 0.1.23"]},{"certainty":"source_listed","source_ids":["sr-9b1f3b69d571bf9c241f09c5a87d5d10"],"technology":"vite","known_exclusions":[],"conditions_summary":"### Summary\n\nThe contents of files that are specified by `server.fs.deny` can be returned to the browser on Windows.\n\n### Impact\n\nOnly apps that match the following conditions are affected:\n\n- explicitly exposes the Vite dev server to the network (using `--host` or `server.host` config option)\n- the sensitive file exists in the allowed directories specified by `server.fs.allow`\n- either of:\n  - the sensitive file exists in an NTFS volume\n  - the dev server is running on Windows and the sensitive file exists in a volume that 8.3 short name generation is enabled (it is enabled by default on system volumes)\n\n### Details\n\nVite’s dev server denies direct access to sensitive files through `server.fs.deny`, including entries such as `.env`, `.env.*`, and `*.{crt,pem}`. However, on Windows, the deny logic does not correctly normalize NTFS ADS path forms before access checks are applied.\nBecause of this, requests such as `/.env::$DATA?raw` are treated as allowed paths, while Windows resolves them to the original file'","public_affected_ranges":["SEMVER: introduced 8.0.0; fixed 8.0.16"]},{"certainty":"source_listed","source_ids":["sr-9b1f3b69d571bf9c241f09c5a87d5d10"],"technology":"vite","known_exclusions":[],"conditions_summary":"### Summary\n\nThe contents of files that are specified by `server.fs.deny` can be returned to the browser on Windows.\n\n### Impact\n\nOnly apps that match the following conditions are affected:\n\n- explicitly exposes the Vite dev server to the network (using `--host` or `server.host` config option)\n- the sensitive file exists in the allowed directories specified by `server.fs.allow`\n- either of:\n  - the sensitive file exists in an NTFS volume\n  - the dev server is running on Windows and the sensitive file exists in a volume that 8.3 short name generation is enabled (it is enabled by default on system volumes)\n\n### Details\n\nVite’s dev server denies direct access to sensitive files through `server.fs.deny`, including entries such as `.env`, `.env.*`, and `*.{crt,pem}`. However, on Windows, the deny logic does not correctly normalize NTFS ADS path forms before access checks are applied.\nBecause of this, requests such as `/.env::$DATA?raw` are treated as allowed paths, while Windows resolves them to the original file'","public_affected_ranges":["SEMVER: introduced 7.0.0; fixed 7.3.5"]},{"certainty":"source_listed","source_ids":["sr-9b1f3b69d571bf9c241f09c5a87d5d10"],"technology":"vite","known_exclusions":[],"conditions_summary":"### Summary\n\nThe contents of files that are specified by `server.fs.deny` can be returned to the browser on Windows.\n\n### Impact\n\nOnly apps that match the following conditions are affected:\n\n- explicitly exposes the Vite dev server to the network (using `--host` or `server.host` config option)\n- the sensitive file exists in the allowed directories specified by `server.fs.allow`\n- either of:\n  - the sensitive file exists in an NTFS volume\n  - the dev server is running on Windows and the sensitive file exists in a volume that 8.3 short name generation is enabled (it is enabled by default on system volumes)\n\n### Details\n\nVite’s dev server denies direct access to sensitive files through `server.fs.deny`, including entries such as `.env`, `.env.*`, and `*.{crt,pem}`. However, on Windows, the deny logic does not correctly normalize NTFS ADS path forms before access checks are applied.\nBecause of this, requests such as `/.env::$DATA?raw` are treated as allowed paths, while Windows resolves them to the original file'","public_affected_ranges":["SEMVER: introduced 0; fixed 6.4.3"]},{"certainty":"source_listed","source_ids":["sr-9b1f3b69d571bf9c241f09c5a87d5d10"],"technology":"vite-plus","known_exclusions":[],"conditions_summary":"### Summary\n\nThe contents of files that are specified by `server.fs.deny` can be returned to the browser on Windows.\n\n### Impact\n\nOnly apps that match the following conditions are affected:\n\n- explicitly exposes the Vite dev server to the network (using `--host` or `server.host` config option)\n- the sensitive file exists in the allowed directories specified by `server.fs.allow`\n- either of:\n  - the sensitive file exists in an NTFS volume\n  - the dev server is running on Windows and the sensitive file exists in a volume that 8.3 short name generation is enabled (it is enabled by default on system volumes)\n\n### Details\n\nVite’s dev server denies direct access to sensitive files through `server.fs.deny`, including entries such as `.env`, `.env.*`, and `*.{crt,pem}`. However, on Windows, the deny logic does not correctly normalize NTFS ADS path forms before access checks are applied.\nBecause of this, requests such as `/.env::$DATA?raw` are treated as allowed paths, while Windows resolves them to the original file'","public_affected_ranges":["SEMVER: introduced 0; fixed 0.1.24"]}],"null_published_at":"2026-11-03T22:39:43.352Z","source_updated_at":"2026-10-27T14:58:31.000Z","source_disclosed_at":"2026-06-15T17:17:45.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-31T22:06:46.371Z"},{"id":"NVI-00010752","kind":"vulnerability","title":"vite: `server.fs.deny` bypass on Windows alternate paths","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-fx2h-pf6j-xcff","CVE-2026-53571"],"plain_summary":"GitHub lists this reviewed advisory for vite, vite, vite, vite-plus. 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-0680a6625510e0d4d85d9167d59eceac"],"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":"0.577%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.47528. Missing scores are unknown.","source_id":"sr-0680a6625510e0d4d85d9167d59eceac"}],"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-e85cc236fa954d073c06cb89e7a62dd4","url":"https://github.com/advisories/GHSA-fx2h-pf6j-xcff","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-fx2h-pf6j-xcff","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T22:06:46.371Z"},{"id":"sr-0680a6625510e0d4d85d9167d59eceac","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-53571","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:15:58.856Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-e85cc236fa954d073c06cb89e7a62dd4"],"technology":"vite","known_exclusions":[],"conditions_summary":"### Summary\n\nThe contents of files that are specified by `server.fs.deny` can be returned to the browser on Windows.\n\n### Impact\n\nOnly apps that match the following conditions are affected:\n\n- explicitly exposes the Vite dev server to the network (using `--host` or `server.host` config option)\n- the sensitive file exists in the allowed directories specified by `server.fs.allow`\n- either of:\n  - the sensitive file exists in an NTFS volume\n  - the dev server is running on Windows and the sensitive file exists in a volume that 8.3 short name generation is enabled (it is enabled by default on system volumes)\n\n### Details\n\nVite’s dev server denies direct access to sensitive files through `server.fs.deny`, including entries such as `.env`, `.env.*`, and `*.{crt,pem}`. However, on Windows, the deny logic does not correctly normalize NTFS ADS path forms before access checks are applied.\nBecause of this, requests such as `/.env::$DATA?raw` are treated as allowed paths, while Windows resolves them to the original file'","public_affected_ranges":[">= 8.0.0, <= 8.0.15"]},{"certainty":"source_listed","source_ids":["sr-e85cc236fa954d073c06cb89e7a62dd4"],"technology":"vite","known_exclusions":[],"conditions_summary":"### Summary\n\nThe contents of files that are specified by `server.fs.deny` can be returned to the browser on Windows.\n\n### Impact\n\nOnly apps that match the following conditions are affected:\n\n- explicitly exposes the Vite dev server to the network (using `--host` or `server.host` config option)\n- the sensitive file exists in the allowed directories specified by `server.fs.allow`\n- either of:\n  - the sensitive file exists in an NTFS volume\n  - the dev server is running on Windows and the sensitive file exists in a volume that 8.3 short name generation is enabled (it is enabled by default on system volumes)\n\n### Details\n\nVite’s dev server denies direct access to sensitive files through `server.fs.deny`, including entries such as `.env`, `.env.*`, and `*.{crt,pem}`. However, on Windows, the deny logic does not correctly normalize NTFS ADS path forms before access checks are applied.\nBecause of this, requests such as `/.env::$DATA?raw` are treated as allowed paths, while Windows resolves them to the original file'","public_affected_ranges":[">= 7.0.0, <= 7.3.4"]},{"certainty":"source_listed","source_ids":["sr-e85cc236fa954d073c06cb89e7a62dd4"],"technology":"vite","known_exclusions":[],"conditions_summary":"### Summary\n\nThe contents of files that are specified by `server.fs.deny` can be returned to the browser on Windows.\n\n### Impact\n\nOnly apps that match the following conditions are affected:\n\n- explicitly exposes the Vite dev server to the network (using `--host` or `server.host` config option)\n- the sensitive file exists in the allowed directories specified by `server.fs.allow`\n- either of:\n  - the sensitive file exists in an NTFS volume\n  - the dev server is running on Windows and the sensitive file exists in a volume that 8.3 short name generation is enabled (it is enabled by default on system volumes)\n\n### Details\n\nVite’s dev server denies direct access to sensitive files through `server.fs.deny`, including entries such as `.env`, `.env.*`, and `*.{crt,pem}`. However, on Windows, the deny logic does not correctly normalize NTFS ADS path forms before access checks are applied.\nBecause of this, requests such as `/.env::$DATA?raw` are treated as allowed paths, while Windows resolves them to the original file'","public_affected_ranges":["<= 6.4.2"]},{"certainty":"source_listed","source_ids":["sr-e85cc236fa954d073c06cb89e7a62dd4"],"technology":"vite-plus","known_exclusions":[],"conditions_summary":"### Summary\n\nThe contents of files that are specified by `server.fs.deny` can be returned to the browser on Windows.\n\n### Impact\n\nOnly apps that match the following conditions are affected:\n\n- explicitly exposes the Vite dev server to the network (using `--host` or `server.host` config option)\n- the sensitive file exists in the allowed directories specified by `server.fs.allow`\n- either of:\n  - the sensitive file exists in an NTFS volume\n  - the dev server is running on Windows and the sensitive file exists in a volume that 8.3 short name generation is enabled (it is enabled by default on system volumes)\n\n### Details\n\nVite’s dev server denies direct access to sensitive files through `server.fs.deny`, including entries such as `.env`, `.env.*`, and `*.{crt,pem}`. However, on Windows, the deny logic does not correctly normalize NTFS ADS path forms before access checks are applied.\nBecause of this, requests such as `/.env::$DATA?raw` are treated as allowed paths, while Windows resolves them to the original file'","public_affected_ranges":["<= 0.1.23"]}],"null_published_at":"2026-11-03T17:49:15.012Z","source_updated_at":"2026-10-27T14:58:31.000Z","source_disclosed_at":"2026-06-15T17:17:45.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-31T22:06:46.371Z"},{"id":"NVI-00010752","kind":"vulnerability","title":"vite: `server.fs.deny` bypass on Windows alternate paths","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-fx2h-pf6j-xcff","CVE-2026-53571"],"plain_summary":"GitHub lists this reviewed advisory for vite, vite, vite, vite-plus. 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-e85cc236fa954d073c06cb89e7a62dd4"],"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":[],"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-e85cc236fa954d073c06cb89e7a62dd4","url":"https://github.com/advisories/GHSA-fx2h-pf6j-xcff","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-fx2h-pf6j-xcff","publisher":"GitHub Advisory Database","observed_at":"2026-10-31T22:06:46.371Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-e85cc236fa954d073c06cb89e7a62dd4"],"technology":"vite","known_exclusions":[],"conditions_summary":"### Summary\n\nThe contents of files that are specified by `server.fs.deny` can be returned to the browser on Windows.\n\n### Impact\n\nOnly apps that match the following conditions are affected:\n\n- explicitly exposes the Vite dev server to the network (using `--host` or `server.host` config option)\n- the sensitive file exists in the allowed directories specified by `server.fs.allow`\n- either of:\n  - the sensitive file exists in an NTFS volume\n  - the dev server is running on Windows and the sensitive file exists in a volume that 8.3 short name generation is enabled (it is enabled by default on system volumes)\n\n### Details\n\nVite’s dev server denies direct access to sensitive files through `server.fs.deny`, including entries such as `.env`, `.env.*`, and `*.{crt,pem}`. However, on Windows, the deny logic does not correctly normalize NTFS ADS path forms before access checks are applied.\nBecause of this, requests such as `/.env::$DATA?raw` are treated as allowed paths, while Windows resolves them to the original file'","public_affected_ranges":[">= 8.0.0, <= 8.0.15"]},{"certainty":"source_listed","source_ids":["sr-e85cc236fa954d073c06cb89e7a62dd4"],"technology":"vite","known_exclusions":[],"conditions_summary":"### Summary\n\nThe contents of files that are specified by `server.fs.deny` can be returned to the browser on Windows.\n\n### Impact\n\nOnly apps that match the following conditions are affected:\n\n- explicitly exposes the Vite dev server to the network (using `--host` or `server.host` config option)\n- the sensitive file exists in the allowed directories specified by `server.fs.allow`\n- either of:\n  - the sensitive file exists in an NTFS volume\n  - the dev server is running on Windows and the sensitive file exists in a volume that 8.3 short name generation is enabled (it is enabled by default on system volumes)\n\n### Details\n\nVite’s dev server denies direct access to sensitive files through `server.fs.deny`, including entries such as `.env`, `.env.*`, and `*.{crt,pem}`. However, on Windows, the deny logic does not correctly normalize NTFS ADS path forms before access checks are applied.\nBecause of this, requests such as `/.env::$DATA?raw` are treated as allowed paths, while Windows resolves them to the original file'","public_affected_ranges":[">= 7.0.0, <= 7.3.4"]},{"certainty":"source_listed","source_ids":["sr-e85cc236fa954d073c06cb89e7a62dd4"],"technology":"vite","known_exclusions":[],"conditions_summary":"### Summary\n\nThe contents of files that are specified by `server.fs.deny` can be returned to the browser on Windows.\n\n### Impact\n\nOnly apps that match the following conditions are affected:\n\n- explicitly exposes the Vite dev server to the network (using `--host` or `server.host` config option)\n- the sensitive file exists in the allowed directories specified by `server.fs.allow`\n- either of:\n  - the sensitive file exists in an NTFS volume\n  - the dev server is running on Windows and the sensitive file exists in a volume that 8.3 short name generation is enabled (it is enabled by default on system volumes)\n\n### Details\n\nVite’s dev server denies direct access to sensitive files through `server.fs.deny`, including entries such as `.env`, `.env.*`, and `*.{crt,pem}`. However, on Windows, the deny logic does not correctly normalize NTFS ADS path forms before access checks are applied.\nBecause of this, requests such as `/.env::$DATA?raw` are treated as allowed paths, while Windows resolves them to the original file'","public_affected_ranges":["<= 6.4.2"]},{"certainty":"source_listed","source_ids":["sr-e85cc236fa954d073c06cb89e7a62dd4"],"technology":"vite-plus","known_exclusions":[],"conditions_summary":"### Summary\n\nThe contents of files that are specified by `server.fs.deny` can be returned to the browser on Windows.\n\n### Impact\n\nOnly apps that match the following conditions are affected:\n\n- explicitly exposes the Vite dev server to the network (using `--host` or `server.host` config option)\n- the sensitive file exists in the allowed directories specified by `server.fs.allow`\n- either of:\n  - the sensitive file exists in an NTFS volume\n  - the dev server is running on Windows and the sensitive file exists in a volume that 8.3 short name generation is enabled (it is enabled by default on system volumes)\n\n### Details\n\nVite’s dev server denies direct access to sensitive files through `server.fs.deny`, including entries such as `.env`, `.env.*`, and `*.{crt,pem}`. However, on Windows, the deny logic does not correctly normalize NTFS ADS path forms before access checks are applied.\nBecause of this, requests such as `/.env::$DATA?raw` are treated as allowed paths, while Windows resolves them to the original file'","public_affected_ranges":["<= 0.1.23"]}],"null_published_at":"2026-10-31T22:27:12.380Z","source_updated_at":"2026-10-27T14:58:31.000Z","source_disclosed_at":"2026-06-15T17:17:45.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-31T22:06:46.371Z"}],"next_cursor":null,"snapshot_revision":"42594"}