{"items":[{"id":"NVI-00003134","kind":"vulnerability","title":"Twig: Sandbox filter, tag and function allow-list bypass when sandbox state changes between renders for a cached `Template`","revision":6,"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-529h-vh3j-85hq","CVE-2026-49981"],"plain_summary":"GitHub lists this reviewed advisory for twig/twig. 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-0f78850c36fd169be8adf87b7cf4f904"],"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 3.27.0 for twig/twig. Confirm the publisher’s latest guidance.","source_ids":["sr-33bc375b5971a8d1ba48177a70bbf82e"],"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-24T22:10:00.210Z","value":"8.2 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-b535d63bd3a61076d16b09a30a692e9b"},{"kind":"CVSS","as_of":"2026-10-24T22:10:00.210Z","value":"6 MEDIUM (4.0)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-b535d63bd3a61076d16b09a30a692e9b"},{"kind":"EPSS","as_of":"2026-11-04T12:03:12.000Z","value":"0.362%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.30135. Missing scores are unknown.","source_id":"sr-0f78850c36fd169be8adf87b7cf4f904"}],"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-743f6f84ff3f646244ab4067fddc3a1f","url":"https://github.com/advisories/GHSA-529h-vh3j-85hq","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-529h-vh3j-85hq","publisher":"GitHub Advisory Database","observed_at":"2026-11-05T03:49:14.191Z"},{"id":"sr-33bc375b5971a8d1ba48177a70bbf82e","url":"https://github.com/advisories/GHSA-529h-vh3j-85hq","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-529h-vh3j-85hq","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.675Z"},{"id":"sr-b535d63bd3a61076d16b09a30a692e9b","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-49981","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-49981","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:24:22.913Z"},{"id":"sr-0f78850c36fd169be8adf87b7cf4f904","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-49981","publisher":"FIRST EPSS","observed_at":"2026-11-04T17:58:50.330Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-743f6f84ff3f646244ab4067fddc3a1f"],"technology":"twig/twig","known_exclusions":[],"conditions_summary":"### Description\n\nThe per-template filter, tag and function allow-list check is compiled into the `checkSecurity()` method of each `Template` subclass and was invoked once from the constructor, gated by `SandboxExtension::isSandboxed($source)`. `Template` instances are then cached on the `Environment` in `$loadedTemplates`, so the verdict computed at construction time was sticky for the rest of the process.\n\nAny later change of sandbox state on the same `Environment` left that cached verdict in place: toggling `SandboxExtension::enableSandbox()`/`disableSandbox()`, swapping the policy via `setSecurityPolicy()`, a `SourcePolicyInterface` decision flip, or simply having a parent, macro or included template pre-instantiated outside the sandbox before a sandboxed render reached it. In all of these cases, the filters, tags and functions used by the affected template kept running with the original (typically empty) check, bypassing the `SecurityPolicy` allow-list.\n\nMethod, property and `__toString` allow-lists are not affected: they are enforced at every call site at runtime through `SandboxExtension::checkMethodAllowed()`, `checkPropertyAllowed()` and `ensureToStringAllowed()`, which re-","public_affected_ranges":["<= 3.26.0"]},{"certainty":"source_listed","source_ids":["sr-33bc375b5971a8d1ba48177a70bbf82e"],"technology":"twig/twig","known_exclusions":[],"conditions_summary":"### Description\n\nThe per-template filter, tag and function allow-list check is compiled into the `checkSecurity()` method of each `Template` subclass and was invoked once from the constructor, gated by `SandboxExtension::isSandboxed($source)`. `Template` instances are then cached on the `Environment` in `$loadedTemplates`, so the verdict computed at construction time was sticky for the rest of the process.\n\nAny later change of sandbox state on the same `Environment` left that cached verdict in place: toggling `SandboxExtension::enableSandbox()`/`disableSandbox()`, swapping the policy via `setSecurityPolicy()`, a `SourcePolicyInterface` decision flip, or simply having a parent, macro or included template pre-instantiated outside the sandbox before a sandboxed render reached it. In all of these cases, the filters, tags and functions used by the affected template kept running with the original (typically empty) check, bypassing the `SecurityPolicy` allow-list.\n\nMethod, property and `__toString` allow-lists are not affected: they are enforced at every call site at runtime through `SandboxExtension::checkMethodAllowed()`, `checkPropertyAllowed()` and `ensureToStringAllowed()`, which re-","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 3.27.0"]}],"null_published_at":"2026-11-07T14:02:01.393Z","source_updated_at":"2026-07-01T18:55:50.000Z","source_disclosed_at":"2026-07-01T18:55:49.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:41:49.675Z"},{"id":"NVI-00003134","kind":"vulnerability","title":"Twig: Sandbox filter, tag and function allow-list bypass when sandbox state changes between renders for a cached `Template`","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-529h-vh3j-85hq","CVE-2026-49981"],"plain_summary":"GitHub lists this reviewed advisory for twig/twig. 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-0141f13d716933f49fe61c6cc1000211"],"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 3.27.0 for twig/twig. Confirm the publisher’s latest guidance.","source_ids":["sr-33bc375b5971a8d1ba48177a70bbf82e"],"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-24T22:10:00.210Z","value":"8.2 HIGH (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-b535d63bd3a61076d16b09a30a692e9b"},{"kind":"CVSS","as_of":"2026-10-24T22:10:00.210Z","value":"6 MEDIUM (4.0)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-b535d63bd3a61076d16b09a30a692e9b"},{"kind":"EPSS","as_of":"2026-11-02T12:00:30.000Z","value":"0.362%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.29978. Missing scores are unknown.","source_id":"sr-0141f13d716933f49fe61c6cc1000211"}],"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-743f6f84ff3f646244ab4067fddc3a1f","url":"https://github.com/advisories/GHSA-529h-vh3j-85hq","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-529h-vh3j-85hq","publisher":"GitHub Advisory Database","observed_at":"2026-11-05T03:49:14.191Z"},{"id":"sr-33bc375b5971a8d1ba48177a70bbf82e","url":"https://github.com/advisories/GHSA-529h-vh3j-85hq","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-529h-vh3j-85hq","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.675Z"},{"id":"sr-b535d63bd3a61076d16b09a30a692e9b","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-49981","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-49981","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:24:22.913Z"},{"id":"sr-0141f13d716933f49fe61c6cc1000211","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-49981","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:15:58.856Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-743f6f84ff3f646244ab4067fddc3a1f"],"technology":"twig/twig","known_exclusions":[],"conditions_summary":"### Description\n\nThe per-template filter, tag and function allow-list check is compiled into the `checkSecurity()` method of each `Template` subclass and was invoked once from the constructor, gated by `SandboxExtension::isSandboxed($source)`. `Template` instances are then cached on the `Environment` in `$loadedTemplates`, so the verdict computed at construction time was sticky for the rest of the process.\n\nAny later change of sandbox state on the same `Environment` left that cached verdict in place: toggling `SandboxExtension::enableSandbox()`/`disableSandbox()`, swapping the policy via `setSecurityPolicy()`, a `SourcePolicyInterface` decision flip, or simply having a parent, macro or included template pre-instantiated outside the sandbox before a sandboxed render reached it. In all of these cases, the filters, tags and functions used by the affected template kept running with the original (typically empty) check, bypassing the `SecurityPolicy` allow-list.\n\nMethod, property and `__toString` allow-lists are not affected: they are enforced at every call site at runtime through `SandboxExtension::checkMethodAllowed()`, `checkPropertyAllowed()` and `ensureToStringAllowed()`, which re-","public_affected_ranges":["<= 3.26.0"]},{"certainty":"source_listed","source_ids":["sr-33bc375b5971a8d1ba48177a70bbf82e"],"technology":"twig/twig","known_exclusions":[],"conditions_summary":"### Description\n\nThe per-template filter, tag and function allow-list check is compiled into the `checkSecurity()` method of each `Template` subclass and was invoked once from the constructor, gated by `SandboxExtension::isSandboxed($source)`. `Template` instances are then cached on the `Environment` in `$loadedTemplates`, so the verdict computed at construction time was sticky for the rest of the process.\n\nAny later change of sandbox state on the same `Environment` left that cached verdict in place: toggling `SandboxExtension::enableSandbox()`/`disableSandbox()`, swapping the policy via `setSecurityPolicy()`, a `SourcePolicyInterface` decision flip, or simply having a parent, macro or included template pre-instantiated outside the sandbox before a sandboxed render reached it. In all of these cases, the filters, tags and functions used by the affected template kept running with the original (typically empty) check, bypassing the `SecurityPolicy` allow-list.\n\nMethod, property and `__toString` allow-lists are not affected: they are enforced at every call site at runtime through `SandboxExtension::checkMethodAllowed()`, `checkPropertyAllowed()` and `ensureToStringAllowed()`, which re-","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 3.27.0"]}],"null_published_at":"2026-11-06T15:18:17.690Z","source_updated_at":"2026-07-01T18:55:50.000Z","source_disclosed_at":"2026-07-01T18:55:49.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:41:49.675Z"},{"id":"NVI-00003134","kind":"vulnerability","title":"Twig: Sandbox filter, tag and function allow-list bypass when sandbox state changes between renders for a cached `Template`","revision":4,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-529h-vh3j-85hq","CVE-2026-49981"],"plain_summary":"GitHub lists this reviewed advisory for twig/twig. 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-0141f13d716933f49fe61c6cc1000211"],"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 3.27.0 for twig/twig. Confirm the publisher’s latest guidance.","source_ids":["sr-33bc375b5971a8d1ba48177a70bbf82e"],"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.362%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.29978. Missing scores are unknown.","source_id":"sr-0141f13d716933f49fe61c6cc1000211"}],"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-743f6f84ff3f646244ab4067fddc3a1f","url":"https://github.com/advisories/GHSA-529h-vh3j-85hq","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-529h-vh3j-85hq","publisher":"GitHub Advisory Database","observed_at":"2026-11-05T03:49:14.191Z"},{"id":"sr-33bc375b5971a8d1ba48177a70bbf82e","url":"https://github.com/advisories/GHSA-529h-vh3j-85hq","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-529h-vh3j-85hq","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.675Z"},{"id":"sr-0141f13d716933f49fe61c6cc1000211","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-49981","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:15:58.856Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-743f6f84ff3f646244ab4067fddc3a1f"],"technology":"twig/twig","known_exclusions":[],"conditions_summary":"### Description\n\nThe per-template filter, tag and function allow-list check is compiled into the `checkSecurity()` method of each `Template` subclass and was invoked once from the constructor, gated by `SandboxExtension::isSandboxed($source)`. `Template` instances are then cached on the `Environment` in `$loadedTemplates`, so the verdict computed at construction time was sticky for the rest of the process.\n\nAny later change of sandbox state on the same `Environment` left that cached verdict in place: toggling `SandboxExtension::enableSandbox()`/`disableSandbox()`, swapping the policy via `setSecurityPolicy()`, a `SourcePolicyInterface` decision flip, or simply having a parent, macro or included template pre-instantiated outside the sandbox before a sandboxed render reached it. In all of these cases, the filters, tags and functions used by the affected template kept running with the original (typically empty) check, bypassing the `SecurityPolicy` allow-list.\n\nMethod, property and `__toString` allow-lists are not affected: they are enforced at every call site at runtime through `SandboxExtension::checkMethodAllowed()`, `checkPropertyAllowed()` and `ensureToStringAllowed()`, which re-","public_affected_ranges":["<= 3.26.0"]},{"certainty":"source_listed","source_ids":["sr-33bc375b5971a8d1ba48177a70bbf82e"],"technology":"twig/twig","known_exclusions":[],"conditions_summary":"### Description\n\nThe per-template filter, tag and function allow-list check is compiled into the `checkSecurity()` method of each `Template` subclass and was invoked once from the constructor, gated by `SandboxExtension::isSandboxed($source)`. `Template` instances are then cached on the `Environment` in `$loadedTemplates`, so the verdict computed at construction time was sticky for the rest of the process.\n\nAny later change of sandbox state on the same `Environment` left that cached verdict in place: toggling `SandboxExtension::enableSandbox()`/`disableSandbox()`, swapping the policy via `setSecurityPolicy()`, a `SourcePolicyInterface` decision flip, or simply having a parent, macro or included template pre-instantiated outside the sandbox before a sandboxed render reached it. In all of these cases, the filters, tags and functions used by the affected template kept running with the original (typically empty) check, bypassing the `SecurityPolicy` allow-list.\n\nMethod, property and `__toString` allow-lists are not affected: they are enforced at every call site at runtime through `SandboxExtension::checkMethodAllowed()`, `checkPropertyAllowed()` and `ensureToStringAllowed()`, which re-","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 3.27.0"]}],"null_published_at":"2026-11-05T19:10:21.477Z","source_updated_at":"2026-07-01T18:55:50.000Z","source_disclosed_at":"2026-07-01T18:55:49.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:41:49.675Z"},{"id":"NVI-00003134","kind":"vulnerability","title":"Twig: Sandbox filter, tag and function allow-list bypass when sandbox state changes between renders for a cached `Template`","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-529h-vh3j-85hq","CVE-2026-49981"],"plain_summary":"OSV carries this publisher advisory for twig/twig. 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 3.27.0 for twig/twig. Confirm the publisher’s latest guidance.","source_ids":["sr-33bc375b5971a8d1ba48177a70bbf82e"],"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-0141f13d716933f49fe61c6cc1000211"],"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.362%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.29978. Missing scores are unknown.","source_id":"sr-0141f13d716933f49fe61c6cc1000211"}],"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-33bc375b5971a8d1ba48177a70bbf82e","url":"https://github.com/advisories/GHSA-529h-vh3j-85hq","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-529h-vh3j-85hq","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.675Z"},{"id":"sr-0141f13d716933f49fe61c6cc1000211","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-49981","publisher":"FIRST EPSS","observed_at":"2026-11-02T20:15:58.856Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-33bc375b5971a8d1ba48177a70bbf82e"],"technology":"twig/twig","known_exclusions":[],"conditions_summary":"### Description\n\nThe per-template filter, tag and function allow-list check is compiled into the `checkSecurity()` method of each `Template` subclass and was invoked once from the constructor, gated by `SandboxExtension::isSandboxed($source)`. `Template` instances are then cached on the `Environment` in `$loadedTemplates`, so the verdict computed at construction time was sticky for the rest of the process.\n\nAny later change of sandbox state on the same `Environment` left that cached verdict in place: toggling `SandboxExtension::enableSandbox()`/`disableSandbox()`, swapping the policy via `setSecurityPolicy()`, a `SourcePolicyInterface` decision flip, or simply having a parent, macro or included template pre-instantiated outside the sandbox before a sandboxed render reached it. In all of these cases, the filters, tags and functions used by the affected template kept running with the original (typically empty) check, bypassing the `SecurityPolicy` allow-list.\n\nMethod, property and `__toString` allow-lists are not affected: they are enforced at every call site at runtime through `SandboxExtension::checkMethodAllowed()`, `checkPropertyAllowed()` and `ensureToStringAllowed()`, which re-","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 3.27.0"]}],"null_published_at":"2026-11-03T17:49:14.972Z","source_updated_at":"2026-09-10T03:51:10.402Z","source_disclosed_at":"2026-07-01T18:55:49.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:41:49.675Z"},{"id":"NVI-00003134","kind":"vulnerability","title":"Twig: Sandbox filter, tag and function allow-list bypass when sandbox state changes between renders for a cached `Template`","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-529h-vh3j-85hq","CVE-2026-49981"],"plain_summary":"OSV carries this publisher advisory for twig/twig. 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 3.27.0 for twig/twig. Confirm the publisher’s latest guidance.","source_ids":["sr-33bc375b5971a8d1ba48177a70bbf82e"],"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-878a3626ea18ba0c1e153978368459eb"],"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.362%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.29994. Missing scores are unknown.","source_id":"sr-878a3626ea18ba0c1e153978368459eb"}],"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-33bc375b5971a8d1ba48177a70bbf82e","url":"https://github.com/advisories/GHSA-529h-vh3j-85hq","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-529h-vh3j-85hq","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.675Z"},{"id":"sr-878a3626ea18ba0c1e153978368459eb","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-49981","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.382Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-33bc375b5971a8d1ba48177a70bbf82e"],"technology":"twig/twig","known_exclusions":[],"conditions_summary":"### Description\n\nThe per-template filter, tag and function allow-list check is compiled into the `checkSecurity()` method of each `Template` subclass and was invoked once from the constructor, gated by `SandboxExtension::isSandboxed($source)`. `Template` instances are then cached on the `Environment` in `$loadedTemplates`, so the verdict computed at construction time was sticky for the rest of the process.\n\nAny later change of sandbox state on the same `Environment` left that cached verdict in place: toggling `SandboxExtension::enableSandbox()`/`disableSandbox()`, swapping the policy via `setSecurityPolicy()`, a `SourcePolicyInterface` decision flip, or simply having a parent, macro or included template pre-instantiated outside the sandbox before a sandboxed render reached it. In all of these cases, the filters, tags and functions used by the affected template kept running with the original (typically empty) check, bypassing the `SecurityPolicy` allow-list.\n\nMethod, property and `__toString` allow-lists are not affected: they are enforced at every call site at runtime through `SandboxExtension::checkMethodAllowed()`, `checkPropertyAllowed()` and `ensureToStringAllowed()`, which re-","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 3.27.0"]}],"null_published_at":"2026-11-03T02:33:09.120Z","source_updated_at":"2026-09-10T03:51:10.402Z","source_disclosed_at":"2026-07-01T18:55:49.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:41:49.675Z"},{"id":"NVI-00003134","kind":"vulnerability","title":"Twig: Sandbox filter, tag and function allow-list bypass when sandbox state changes between renders for a cached `Template`","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-529h-vh3j-85hq","CVE-2026-49981"],"plain_summary":"OSV carries this publisher advisory for twig/twig. 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 3.27.0 for twig/twig. Confirm the publisher’s latest guidance.","source_ids":["sr-33bc375b5971a8d1ba48177a70bbf82e"],"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-33bc375b5971a8d1ba48177a70bbf82e","url":"https://github.com/advisories/GHSA-529h-vh3j-85hq","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-529h-vh3j-85hq","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.675Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-33bc375b5971a8d1ba48177a70bbf82e"],"technology":"twig/twig","known_exclusions":[],"conditions_summary":"### Description\n\nThe per-template filter, tag and function allow-list check is compiled into the `checkSecurity()` method of each `Template` subclass and was invoked once from the constructor, gated by `SandboxExtension::isSandboxed($source)`. `Template` instances are then cached on the `Environment` in `$loadedTemplates`, so the verdict computed at construction time was sticky for the rest of the process.\n\nAny later change of sandbox state on the same `Environment` left that cached verdict in place: toggling `SandboxExtension::enableSandbox()`/`disableSandbox()`, swapping the policy via `setSecurityPolicy()`, a `SourcePolicyInterface` decision flip, or simply having a parent, macro or included template pre-instantiated outside the sandbox before a sandboxed render reached it. In all of these cases, the filters, tags and functions used by the affected template kept running with the original (typically empty) check, bypassing the `SecurityPolicy` allow-list.\n\nMethod, property and `__toString` allow-lists are not affected: they are enforced at every call site at runtime through `SandboxExtension::checkMethodAllowed()`, `checkPropertyAllowed()` and `ensureToStringAllowed()`, which re-","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 3.27.0"]}],"null_published_at":"2026-10-31T22:12:38.476Z","source_updated_at":"2026-09-10T03:51:10.402Z","source_disclosed_at":"2026-07-01T18:55:49.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:41:49.675Z"}],"next_cursor":null,"snapshot_revision":"42594"}