{"items":[{"id":"NVI-00003536","kind":"vulnerability","title":"Gadget chain in Symfony 1 due to vulnerable Swift Mailer dependency","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-wjv8-pxr6-5f4r","CVE-2024-28859"],"plain_summary":"OSV carries this publisher advisory for friendsofsymfony1/symfony1, friendsofsymfony1/swiftmailer, friendsofsymfony1/swiftmailer, swiftmailer/swiftmailer. 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 1.5.18 for friendsofsymfony1/symfony1. Confirm the publisher’s latest guidance.","source_ids":["sr-41fb1ebd6c81bb6987142a5a31acdbe6"],"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 5.4.13 for friendsofsymfony1/swiftmailer. Confirm the publisher’s latest guidance.","source_ids":["sr-41fb1ebd6c81bb6987142a5a31acdbe6"],"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.2.5 for friendsofsymfony1/swiftmailer. Confirm the publisher’s latest guidance.","source_ids":["sr-41fb1ebd6c81bb6987142a5a31acdbe6"],"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.2.5 for swiftmailer/swiftmailer. Confirm the publisher’s latest guidance.","source_ids":["sr-41fb1ebd6c81bb6987142a5a31acdbe6"],"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-2930c69a280fe49625232faf7ecae44b"],"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-06-17T07:21:54.103Z","value":"5 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-8e3d1e732f7a894591604b7fd2903f15"},{"kind":"CVSS","as_of":"2026-06-17T07:21:54.103Z","value":"9 CRITICAL (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-8e3d1e732f7a894591604b7fd2903f15"},{"kind":"EPSS","as_of":"2026-11-03T12:00:27.000Z","value":"1.594%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.7574. Missing scores are unknown.","source_id":"sr-2930c69a280fe49625232faf7ecae44b"}],"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-41fb1ebd6c81bb6987142a5a31acdbe6","url":"https://github.com/advisories/GHSA-wjv8-pxr6-5f4r","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-wjv8-pxr6-5f4r","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.388Z"},{"id":"sr-8e3d1e732f7a894591604b7fd2903f15","url":"https://nvd.nist.gov/vuln/detail/CVE-2024-28859","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2024-28859","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T00:59:14.650Z"},{"id":"sr-2930c69a280fe49625232faf7ecae44b","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-2024-28859","publisher":"FIRST EPSS","observed_at":"2026-11-03T17:42:56.080Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-41fb1ebd6c81bb6987142a5a31acdbe6"],"technology":"friendsofsymfony1/symfony1","known_exclusions":[],"conditions_summary":"### Summary\nSymfony 1 has a gadget chain due to vulnerable Swift Mailer dependency that would enable an attacker to get remote code execution if a developer unserialize user input in his project.\n\n### Details\nThis vulnerability present no direct threat but is a vector that will enable remote code execution if a developper deserialize user untrusted data. For example:\n```php\n public function executeIndex(sfWebRequest $request)\n  {\n    $a = unserialize($request->getParameter('user'));\n  }\n```\n\nWe will make the assumption this is the case in the rest of this explanation.\n\nSymfony 1 depends on Swift Mailer which is bundled by default in `vendor` directory in the default installation since 1.3.0. Swift Mailer classes implement some `__destruct()` methods like for instance `Swift_KeyCache_DiskKeyCache` :\n```php\n  public function __destruct()\n  {\n    foreach ($this->_keys as $nsKey=>$null)\n    {\n      $this->clearAll($nsKey);\n    }\n  }\n```\n\nThis method is called when php destroy the object in memory. However, it is possible to include any object type in `$this->_keys` to make PHP access to another array/object properties than intended by the developer. In particular, it is possible to abu","public_affected_ranges":["ECOSYSTEM: introduced 1.3.0; fixed 1.5.18"]},{"certainty":"source_listed","source_ids":["sr-41fb1ebd6c81bb6987142a5a31acdbe6"],"technology":"friendsofsymfony1/swiftmailer","known_exclusions":[],"conditions_summary":"### Summary\nSymfony 1 has a gadget chain due to vulnerable Swift Mailer dependency that would enable an attacker to get remote code execution if a developer unserialize user input in his project.\n\n### Details\nThis vulnerability present no direct threat but is a vector that will enable remote code execution if a developper deserialize user untrusted data. For example:\n```php\n public function executeIndex(sfWebRequest $request)\n  {\n    $a = unserialize($request->getParameter('user'));\n  }\n```\n\nWe will make the assumption this is the case in the rest of this explanation.\n\nSymfony 1 depends on Swift Mailer which is bundled by default in `vendor` directory in the default installation since 1.3.0. Swift Mailer classes implement some `__destruct()` methods like for instance `Swift_KeyCache_DiskKeyCache` :\n```php\n  public function __destruct()\n  {\n    foreach ($this->_keys as $nsKey=>$null)\n    {\n      $this->clearAll($nsKey);\n    }\n  }\n```\n\nThis method is called when php destroy the object in memory. However, it is possible to include any object type in `$this->_keys` to make PHP access to another array/object properties than intended by the developer. In particular, it is possible to abu","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0; fixed 5.4.13"]},{"certainty":"source_listed","source_ids":["sr-41fb1ebd6c81bb6987142a5a31acdbe6"],"technology":"friendsofsymfony1/swiftmailer","known_exclusions":[],"conditions_summary":"### Summary\nSymfony 1 has a gadget chain due to vulnerable Swift Mailer dependency that would enable an attacker to get remote code execution if a developer unserialize user input in his project.\n\n### Details\nThis vulnerability present no direct threat but is a vector that will enable remote code execution if a developper deserialize user untrusted data. For example:\n```php\n public function executeIndex(sfWebRequest $request)\n  {\n    $a = unserialize($request->getParameter('user'));\n  }\n```\n\nWe will make the assumption this is the case in the rest of this explanation.\n\nSymfony 1 depends on Swift Mailer which is bundled by default in `vendor` directory in the default installation since 1.3.0. Swift Mailer classes implement some `__destruct()` methods like for instance `Swift_KeyCache_DiskKeyCache` :\n```php\n  public function __destruct()\n  {\n    foreach ($this->_keys as $nsKey=>$null)\n    {\n      $this->clearAll($nsKey);\n    }\n  }\n```\n\nThis method is called when php destroy the object in memory. However, it is possible to include any object type in `$this->_keys` to make PHP access to another array/object properties than intended by the developer. In particular, it is possible to abu","public_affected_ranges":["ECOSYSTEM: introduced 6.0.0; fixed 6.2.5"]},{"certainty":"source_listed","source_ids":["sr-41fb1ebd6c81bb6987142a5a31acdbe6"],"technology":"swiftmailer/swiftmailer","known_exclusions":[],"conditions_summary":"### Summary\nSymfony 1 has a gadget chain due to vulnerable Swift Mailer dependency that would enable an attacker to get remote code execution if a developer unserialize user input in his project.\n\n### Details\nThis vulnerability present no direct threat but is a vector that will enable remote code execution if a developper deserialize user untrusted data. For example:\n```php\n public function executeIndex(sfWebRequest $request)\n  {\n    $a = unserialize($request->getParameter('user'));\n  }\n```\n\nWe will make the assumption this is the case in the rest of this explanation.\n\nSymfony 1 depends on Swift Mailer which is bundled by default in `vendor` directory in the default installation since 1.3.0. Swift Mailer classes implement some `__destruct()` methods like for instance `Swift_KeyCache_DiskKeyCache` :\n```php\n  public function __destruct()\n  {\n    foreach ($this->_keys as $nsKey=>$null)\n    {\n      $this->clearAll($nsKey);\n    }\n  }\n```\n\nThis method is called when php destroy the object in memory. However, it is possible to include any object type in `$this->_keys` to make PHP access to another array/object properties than intended by the developer. In particular, it is possible to abu","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0; fixed 6.2.5"]}],"null_published_at":"2026-11-08T19:53:33.623Z","source_updated_at":"2026-09-10T03:50:10.958Z","source_disclosed_at":"2024-03-18T20:36:06.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:41.388Z"},{"id":"NVI-00003536","kind":"vulnerability","title":"Gadget chain in Symfony 1 due to vulnerable Swift Mailer dependency","revision":2,"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-wjv8-pxr6-5f4r","CVE-2024-28859"],"plain_summary":"OSV carries this publisher advisory for friendsofsymfony1/symfony1, friendsofsymfony1/swiftmailer, friendsofsymfony1/swiftmailer, swiftmailer/swiftmailer. 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 1.5.18 for friendsofsymfony1/symfony1. Confirm the publisher’s latest guidance.","source_ids":["sr-41fb1ebd6c81bb6987142a5a31acdbe6"],"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 5.4.13 for friendsofsymfony1/swiftmailer. Confirm the publisher’s latest guidance.","source_ids":["sr-41fb1ebd6c81bb6987142a5a31acdbe6"],"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.2.5 for friendsofsymfony1/swiftmailer. Confirm the publisher’s latest guidance.","source_ids":["sr-41fb1ebd6c81bb6987142a5a31acdbe6"],"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.2.5 for swiftmailer/swiftmailer. Confirm the publisher’s latest guidance.","source_ids":["sr-41fb1ebd6c81bb6987142a5a31acdbe6"],"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-8e3d1e732f7a894591604b7fd2903f15"],"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-06-17T07:21:54.103Z","value":"5 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-8e3d1e732f7a894591604b7fd2903f15"},{"kind":"CVSS","as_of":"2026-06-17T07:21:54.103Z","value":"9 CRITICAL (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-8e3d1e732f7a894591604b7fd2903f15"}],"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-41fb1ebd6c81bb6987142a5a31acdbe6","url":"https://github.com/advisories/GHSA-wjv8-pxr6-5f4r","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-wjv8-pxr6-5f4r","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.388Z"},{"id":"sr-8e3d1e732f7a894591604b7fd2903f15","url":"https://nvd.nist.gov/vuln/detail/CVE-2024-28859","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2024-28859","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T00:59:14.650Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-41fb1ebd6c81bb6987142a5a31acdbe6"],"technology":"friendsofsymfony1/symfony1","known_exclusions":[],"conditions_summary":"### Summary\nSymfony 1 has a gadget chain due to vulnerable Swift Mailer dependency that would enable an attacker to get remote code execution if a developer unserialize user input in his project.\n\n### Details\nThis vulnerability present no direct threat but is a vector that will enable remote code execution if a developper deserialize user untrusted data. For example:\n```php\n public function executeIndex(sfWebRequest $request)\n  {\n    $a = unserialize($request->getParameter('user'));\n  }\n```\n\nWe will make the assumption this is the case in the rest of this explanation.\n\nSymfony 1 depends on Swift Mailer which is bundled by default in `vendor` directory in the default installation since 1.3.0. Swift Mailer classes implement some `__destruct()` methods like for instance `Swift_KeyCache_DiskKeyCache` :\n```php\n  public function __destruct()\n  {\n    foreach ($this->_keys as $nsKey=>$null)\n    {\n      $this->clearAll($nsKey);\n    }\n  }\n```\n\nThis method is called when php destroy the object in memory. However, it is possible to include any object type in `$this->_keys` to make PHP access to another array/object properties than intended by the developer. In particular, it is possible to abu","public_affected_ranges":["ECOSYSTEM: introduced 1.3.0; fixed 1.5.18"]},{"certainty":"source_listed","source_ids":["sr-41fb1ebd6c81bb6987142a5a31acdbe6"],"technology":"friendsofsymfony1/swiftmailer","known_exclusions":[],"conditions_summary":"### Summary\nSymfony 1 has a gadget chain due to vulnerable Swift Mailer dependency that would enable an attacker to get remote code execution if a developer unserialize user input in his project.\n\n### Details\nThis vulnerability present no direct threat but is a vector that will enable remote code execution if a developper deserialize user untrusted data. For example:\n```php\n public function executeIndex(sfWebRequest $request)\n  {\n    $a = unserialize($request->getParameter('user'));\n  }\n```\n\nWe will make the assumption this is the case in the rest of this explanation.\n\nSymfony 1 depends on Swift Mailer which is bundled by default in `vendor` directory in the default installation since 1.3.0. Swift Mailer classes implement some `__destruct()` methods like for instance `Swift_KeyCache_DiskKeyCache` :\n```php\n  public function __destruct()\n  {\n    foreach ($this->_keys as $nsKey=>$null)\n    {\n      $this->clearAll($nsKey);\n    }\n  }\n```\n\nThis method is called when php destroy the object in memory. However, it is possible to include any object type in `$this->_keys` to make PHP access to another array/object properties than intended by the developer. In particular, it is possible to abu","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0; fixed 5.4.13"]},{"certainty":"source_listed","source_ids":["sr-41fb1ebd6c81bb6987142a5a31acdbe6"],"technology":"friendsofsymfony1/swiftmailer","known_exclusions":[],"conditions_summary":"### Summary\nSymfony 1 has a gadget chain due to vulnerable Swift Mailer dependency that would enable an attacker to get remote code execution if a developer unserialize user input in his project.\n\n### Details\nThis vulnerability present no direct threat but is a vector that will enable remote code execution if a developper deserialize user untrusted data. For example:\n```php\n public function executeIndex(sfWebRequest $request)\n  {\n    $a = unserialize($request->getParameter('user'));\n  }\n```\n\nWe will make the assumption this is the case in the rest of this explanation.\n\nSymfony 1 depends on Swift Mailer which is bundled by default in `vendor` directory in the default installation since 1.3.0. Swift Mailer classes implement some `__destruct()` methods like for instance `Swift_KeyCache_DiskKeyCache` :\n```php\n  public function __destruct()\n  {\n    foreach ($this->_keys as $nsKey=>$null)\n    {\n      $this->clearAll($nsKey);\n    }\n  }\n```\n\nThis method is called when php destroy the object in memory. However, it is possible to include any object type in `$this->_keys` to make PHP access to another array/object properties than intended by the developer. In particular, it is possible to abu","public_affected_ranges":["ECOSYSTEM: introduced 6.0.0; fixed 6.2.5"]},{"certainty":"source_listed","source_ids":["sr-41fb1ebd6c81bb6987142a5a31acdbe6"],"technology":"swiftmailer/swiftmailer","known_exclusions":[],"conditions_summary":"### Summary\nSymfony 1 has a gadget chain due to vulnerable Swift Mailer dependency that would enable an attacker to get remote code execution if a developer unserialize user input in his project.\n\n### Details\nThis vulnerability present no direct threat but is a vector that will enable remote code execution if a developper deserialize user untrusted data. For example:\n```php\n public function executeIndex(sfWebRequest $request)\n  {\n    $a = unserialize($request->getParameter('user'));\n  }\n```\n\nWe will make the assumption this is the case in the rest of this explanation.\n\nSymfony 1 depends on Swift Mailer which is bundled by default in `vendor` directory in the default installation since 1.3.0. Swift Mailer classes implement some `__destruct()` methods like for instance `Swift_KeyCache_DiskKeyCache` :\n```php\n  public function __destruct()\n  {\n    foreach ($this->_keys as $nsKey=>$null)\n    {\n      $this->clearAll($nsKey);\n    }\n  }\n```\n\nThis method is called when php destroy the object in memory. However, it is possible to include any object type in `$this->_keys` to make PHP access to another array/object properties than intended by the developer. In particular, it is possible to abu","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0; fixed 6.2.5"]}],"null_published_at":"2026-11-03T17:49:21.370Z","source_updated_at":"2026-09-10T03:50:10.958Z","source_disclosed_at":"2024-03-18T20:36:06.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:41.388Z"},{"id":"NVI-00003536","kind":"vulnerability","title":"Gadget chain in Symfony 1 due to vulnerable Swift Mailer dependency","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-wjv8-pxr6-5f4r","CVE-2024-28859"],"plain_summary":"OSV carries this publisher advisory for friendsofsymfony1/symfony1, friendsofsymfony1/swiftmailer, friendsofsymfony1/swiftmailer, swiftmailer/swiftmailer. 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 1.5.18 for friendsofsymfony1/symfony1. Confirm the publisher’s latest guidance.","source_ids":["sr-41fb1ebd6c81bb6987142a5a31acdbe6"],"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 5.4.13 for friendsofsymfony1/swiftmailer. Confirm the publisher’s latest guidance.","source_ids":["sr-41fb1ebd6c81bb6987142a5a31acdbe6"],"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.2.5 for friendsofsymfony1/swiftmailer. Confirm the publisher’s latest guidance.","source_ids":["sr-41fb1ebd6c81bb6987142a5a31acdbe6"],"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.2.5 for swiftmailer/swiftmailer. Confirm the publisher’s latest guidance.","source_ids":["sr-41fb1ebd6c81bb6987142a5a31acdbe6"],"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-41fb1ebd6c81bb6987142a5a31acdbe6","url":"https://github.com/advisories/GHSA-wjv8-pxr6-5f4r","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-wjv8-pxr6-5f4r","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.388Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-41fb1ebd6c81bb6987142a5a31acdbe6"],"technology":"friendsofsymfony1/symfony1","known_exclusions":[],"conditions_summary":"### Summary\nSymfony 1 has a gadget chain due to vulnerable Swift Mailer dependency that would enable an attacker to get remote code execution if a developer unserialize user input in his project.\n\n### Details\nThis vulnerability present no direct threat but is a vector that will enable remote code execution if a developper deserialize user untrusted data. For example:\n```php\n public function executeIndex(sfWebRequest $request)\n  {\n    $a = unserialize($request->getParameter('user'));\n  }\n```\n\nWe will make the assumption this is the case in the rest of this explanation.\n\nSymfony 1 depends on Swift Mailer which is bundled by default in `vendor` directory in the default installation since 1.3.0. Swift Mailer classes implement some `__destruct()` methods like for instance `Swift_KeyCache_DiskKeyCache` :\n```php\n  public function __destruct()\n  {\n    foreach ($this->_keys as $nsKey=>$null)\n    {\n      $this->clearAll($nsKey);\n    }\n  }\n```\n\nThis method is called when php destroy the object in memory. However, it is possible to include any object type in `$this->_keys` to make PHP access to another array/object properties than intended by the developer. In particular, it is possible to abu","public_affected_ranges":["ECOSYSTEM: introduced 1.3.0; fixed 1.5.18"]},{"certainty":"source_listed","source_ids":["sr-41fb1ebd6c81bb6987142a5a31acdbe6"],"technology":"friendsofsymfony1/swiftmailer","known_exclusions":[],"conditions_summary":"### Summary\nSymfony 1 has a gadget chain due to vulnerable Swift Mailer dependency that would enable an attacker to get remote code execution if a developer unserialize user input in his project.\n\n### Details\nThis vulnerability present no direct threat but is a vector that will enable remote code execution if a developper deserialize user untrusted data. For example:\n```php\n public function executeIndex(sfWebRequest $request)\n  {\n    $a = unserialize($request->getParameter('user'));\n  }\n```\n\nWe will make the assumption this is the case in the rest of this explanation.\n\nSymfony 1 depends on Swift Mailer which is bundled by default in `vendor` directory in the default installation since 1.3.0. Swift Mailer classes implement some `__destruct()` methods like for instance `Swift_KeyCache_DiskKeyCache` :\n```php\n  public function __destruct()\n  {\n    foreach ($this->_keys as $nsKey=>$null)\n    {\n      $this->clearAll($nsKey);\n    }\n  }\n```\n\nThis method is called when php destroy the object in memory. However, it is possible to include any object type in `$this->_keys` to make PHP access to another array/object properties than intended by the developer. In particular, it is possible to abu","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0; fixed 5.4.13"]},{"certainty":"source_listed","source_ids":["sr-41fb1ebd6c81bb6987142a5a31acdbe6"],"technology":"friendsofsymfony1/swiftmailer","known_exclusions":[],"conditions_summary":"### Summary\nSymfony 1 has a gadget chain due to vulnerable Swift Mailer dependency that would enable an attacker to get remote code execution if a developer unserialize user input in his project.\n\n### Details\nThis vulnerability present no direct threat but is a vector that will enable remote code execution if a developper deserialize user untrusted data. For example:\n```php\n public function executeIndex(sfWebRequest $request)\n  {\n    $a = unserialize($request->getParameter('user'));\n  }\n```\n\nWe will make the assumption this is the case in the rest of this explanation.\n\nSymfony 1 depends on Swift Mailer which is bundled by default in `vendor` directory in the default installation since 1.3.0. Swift Mailer classes implement some `__destruct()` methods like for instance `Swift_KeyCache_DiskKeyCache` :\n```php\n  public function __destruct()\n  {\n    foreach ($this->_keys as $nsKey=>$null)\n    {\n      $this->clearAll($nsKey);\n    }\n  }\n```\n\nThis method is called when php destroy the object in memory. However, it is possible to include any object type in `$this->_keys` to make PHP access to another array/object properties than intended by the developer. In particular, it is possible to abu","public_affected_ranges":["ECOSYSTEM: introduced 6.0.0; fixed 6.2.5"]},{"certainty":"source_listed","source_ids":["sr-41fb1ebd6c81bb6987142a5a31acdbe6"],"technology":"swiftmailer/swiftmailer","known_exclusions":[],"conditions_summary":"### Summary\nSymfony 1 has a gadget chain due to vulnerable Swift Mailer dependency that would enable an attacker to get remote code execution if a developer unserialize user input in his project.\n\n### Details\nThis vulnerability present no direct threat but is a vector that will enable remote code execution if a developper deserialize user untrusted data. For example:\n```php\n public function executeIndex(sfWebRequest $request)\n  {\n    $a = unserialize($request->getParameter('user'));\n  }\n```\n\nWe will make the assumption this is the case in the rest of this explanation.\n\nSymfony 1 depends on Swift Mailer which is bundled by default in `vendor` directory in the default installation since 1.3.0. Swift Mailer classes implement some `__destruct()` methods like for instance `Swift_KeyCache_DiskKeyCache` :\n```php\n  public function __destruct()\n  {\n    foreach ($this->_keys as $nsKey=>$null)\n    {\n      $this->clearAll($nsKey);\n    }\n  }\n```\n\nThis method is called when php destroy the object in memory. However, it is possible to include any object type in `$this->_keys` to make PHP access to another array/object properties than intended by the developer. In particular, it is possible to abu","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0; fixed 6.2.5"]}],"null_published_at":"2026-10-31T22:12:48.020Z","source_updated_at":"2026-09-10T03:50:10.958Z","source_disclosed_at":"2024-03-18T20:36:06.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:41.388Z"}],"next_cursor":null,"snapshot_revision":"42594"}