{"items":[{"id":"NVI-00002792","kind":"vulnerability","title":"TYPO3 CMS has Broken Access Control in its File Abstraction Layer","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-jf56-v8jc-jcc5","CVE-2026-49738"],"plain_summary":"GitHub lists this reviewed advisory for typo3/cms-core, typo3/cms-core, typo3/cms-core, typo3/cms-core, typo3/cms-core. 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-595ad8ec33990b27fca16fc1b6bfcec2"],"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 10.4.57 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-26f7d9bdded8cdc8c9badd7b399dc99e"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 11.5.51 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-26f7d9bdded8cdc8c9badd7b399dc99e"],"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 12.4.46 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-26f7d9bdded8cdc8c9badd7b399dc99e"],"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 13.4.31 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-26f7d9bdded8cdc8c9badd7b399dc99e"],"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 14.3.3 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-26f7d9bdded8cdc8c9badd7b399dc99e"],"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-07-23T08:10:00.137Z","value":"2.1 LOW (4.0)","meaning":"f4fb688c-4412-4426-b4b8-421ecf27b14a severity; no combined Null risk score.","source_id":"sr-595ad8ec33990b27fca16fc1b6bfcec2"}],"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-1110e0993869a379fd44e937fda7311a","url":"https://github.com/advisories/GHSA-jf56-v8jc-jcc5","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-jf56-v8jc-jcc5","publisher":"GitHub Advisory Database","observed_at":"2026-11-06T15:13:13.153Z"},{"id":"sr-26f7d9bdded8cdc8c9badd7b399dc99e","url":"https://github.com/advisories/GHSA-jf56-v8jc-jcc5","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-jf56-v8jc-jcc5","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:20.441Z"},{"id":"sr-595ad8ec33990b27fca16fc1b6bfcec2","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-49738","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-49738","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:24:22.913Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-1110e0993869a379fd44e937fda7311a"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nThe path allowance check in `GeneralUtility::isAllowedAbsPath()` performed a plain string prefix comparison without requiring a directory separator boundary, causing a path like `/var/www/html-other/secret.yaml` to be incorrectly accepted as valid when the project root was `/var/www/html`. Administrator users with access to the File Abstraction Layer were able to create new file storage definitions pointing to directories outside the project root, bypassing this path check.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Wolfgang Klinger for reporting this issue, and to TYPO3 core & security team member Oliver Hader for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-016","public_affected_ranges":["< 10.4.57"]},{"certainty":"source_listed","source_ids":["sr-1110e0993869a379fd44e937fda7311a"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nThe path allowance check in `GeneralUtility::isAllowedAbsPath()` performed a plain string prefix comparison without requiring a directory separator boundary, causing a path like `/var/www/html-other/secret.yaml` to be incorrectly accepted as valid when the project root was `/var/www/html`. Administrator users with access to the File Abstraction Layer were able to create new file storage definitions pointing to directories outside the project root, bypassing this path check.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Wolfgang Klinger for reporting this issue, and to TYPO3 core & security team member Oliver Hader for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-016","public_affected_ranges":[">= 11.0.0, < 11.5.51"]},{"certainty":"source_listed","source_ids":["sr-1110e0993869a379fd44e937fda7311a"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nThe path allowance check in `GeneralUtility::isAllowedAbsPath()` performed a plain string prefix comparison without requiring a directory separator boundary, causing a path like `/var/www/html-other/secret.yaml` to be incorrectly accepted as valid when the project root was `/var/www/html`. Administrator users with access to the File Abstraction Layer were able to create new file storage definitions pointing to directories outside the project root, bypassing this path check.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Wolfgang Klinger for reporting this issue, and to TYPO3 core & security team member Oliver Hader for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-016","public_affected_ranges":[">= 12.0.0, < 12.4.46"]},{"certainty":"source_listed","source_ids":["sr-1110e0993869a379fd44e937fda7311a"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nThe path allowance check in `GeneralUtility::isAllowedAbsPath()` performed a plain string prefix comparison without requiring a directory separator boundary, causing a path like `/var/www/html-other/secret.yaml` to be incorrectly accepted as valid when the project root was `/var/www/html`. Administrator users with access to the File Abstraction Layer were able to create new file storage definitions pointing to directories outside the project root, bypassing this path check.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Wolfgang Klinger for reporting this issue, and to TYPO3 core & security team member Oliver Hader for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-016","public_affected_ranges":[">= 13.0.0, < 13.4.31"]},{"certainty":"source_listed","source_ids":["sr-1110e0993869a379fd44e937fda7311a"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nThe path allowance check in `GeneralUtility::isAllowedAbsPath()` performed a plain string prefix comparison without requiring a directory separator boundary, causing a path like `/var/www/html-other/secret.yaml` to be incorrectly accepted as valid when the project root was `/var/www/html`. Administrator users with access to the File Abstraction Layer were able to create new file storage definitions pointing to directories outside the project root, bypassing this path check.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Wolfgang Klinger for reporting this issue, and to TYPO3 core & security team member Oliver Hader for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-016","public_affected_ranges":[">= 14.0.0, < 14.3.3"]},{"certainty":"source_listed","source_ids":["sr-26f7d9bdded8cdc8c9badd7b399dc99e"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nThe path allowance check in `GeneralUtility::isAllowedAbsPath()` performed a plain string prefix comparison without requiring a directory separator boundary, causing a path like `/var/www/html-other/secret.yaml` to be incorrectly accepted as valid when the project root was `/var/www/html`. Administrator users with access to the File Abstraction Layer were able to create new file storage definitions pointing to directories outside the project root, bypassing this path check.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Wolfgang Klinger for reporting this issue, and to TYPO3 core & security team member Oliver Hader for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-016","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 10.4.57"]},{"certainty":"source_listed","source_ids":["sr-26f7d9bdded8cdc8c9badd7b399dc99e"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nThe path allowance check in `GeneralUtility::isAllowedAbsPath()` performed a plain string prefix comparison without requiring a directory separator boundary, causing a path like `/var/www/html-other/secret.yaml` to be incorrectly accepted as valid when the project root was `/var/www/html`. Administrator users with access to the File Abstraction Layer were able to create new file storage definitions pointing to directories outside the project root, bypassing this path check.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Wolfgang Klinger for reporting this issue, and to TYPO3 core & security team member Oliver Hader for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-016","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.51"]},{"certainty":"source_listed","source_ids":["sr-26f7d9bdded8cdc8c9badd7b399dc99e"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nThe path allowance check in `GeneralUtility::isAllowedAbsPath()` performed a plain string prefix comparison without requiring a directory separator boundary, causing a path like `/var/www/html-other/secret.yaml` to be incorrectly accepted as valid when the project root was `/var/www/html`. Administrator users with access to the File Abstraction Layer were able to create new file storage definitions pointing to directories outside the project root, bypassing this path check.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Wolfgang Klinger for reporting this issue, and to TYPO3 core & security team member Oliver Hader for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-016","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0; fixed 12.4.46"]},{"certainty":"source_listed","source_ids":["sr-26f7d9bdded8cdc8c9badd7b399dc99e"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nThe path allowance check in `GeneralUtility::isAllowedAbsPath()` performed a plain string prefix comparison without requiring a directory separator boundary, causing a path like `/var/www/html-other/secret.yaml` to be incorrectly accepted as valid when the project root was `/var/www/html`. Administrator users with access to the File Abstraction Layer were able to create new file storage definitions pointing to directories outside the project root, bypassing this path check.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Wolfgang Klinger for reporting this issue, and to TYPO3 core & security team member Oliver Hader for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-016","public_affected_ranges":["ECOSYSTEM: introduced 13.0.0; fixed 13.4.31"]},{"certainty":"source_listed","source_ids":["sr-26f7d9bdded8cdc8c9badd7b399dc99e"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nThe path allowance check in `GeneralUtility::isAllowedAbsPath()` performed a plain string prefix comparison without requiring a directory separator boundary, causing a path like `/var/www/html-other/secret.yaml` to be incorrectly accepted as valid when the project root was `/var/www/html`. Administrator users with access to the File Abstraction Layer were able to create new file storage definitions pointing to directories outside the project root, bypassing this path check.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Wolfgang Klinger for reporting this issue, and to TYPO3 core & security team member Oliver Hader for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-016","public_affected_ranges":["ECOSYSTEM: introduced 14.0.0; fixed 14.3.3"]}],"null_published_at":"2026-11-07T07:07:39.812Z","source_updated_at":"2026-06-12T19:09:05.000Z","source_disclosed_at":"2026-06-12T19:09:04.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:20.441Z"},{"id":"NVI-00002792","kind":"vulnerability","title":"TYPO3 CMS has Broken Access Control in its File Abstraction Layer","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-jf56-v8jc-jcc5","CVE-2026-49738"],"plain_summary":"OSV carries this publisher advisory for typo3/cms-core, typo3/cms-core, typo3/cms-core, typo3/cms-core, typo3/cms-core. 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 10.4.57 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-26f7d9bdded8cdc8c9badd7b399dc99e"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 11.5.51 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-26f7d9bdded8cdc8c9badd7b399dc99e"],"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 12.4.46 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-26f7d9bdded8cdc8c9badd7b399dc99e"],"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 13.4.31 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-26f7d9bdded8cdc8c9badd7b399dc99e"],"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 14.3.3 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-26f7d9bdded8cdc8c9badd7b399dc99e"],"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-595ad8ec33990b27fca16fc1b6bfcec2"],"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-07-23T08:10:00.137Z","value":"2.1 LOW (4.0)","meaning":"f4fb688c-4412-4426-b4b8-421ecf27b14a severity; no combined Null risk score.","source_id":"sr-595ad8ec33990b27fca16fc1b6bfcec2"}],"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-26f7d9bdded8cdc8c9badd7b399dc99e","url":"https://github.com/advisories/GHSA-jf56-v8jc-jcc5","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-jf56-v8jc-jcc5","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:20.441Z"},{"id":"sr-595ad8ec33990b27fca16fc1b6bfcec2","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-49738","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-49738","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:24:22.913Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-26f7d9bdded8cdc8c9badd7b399dc99e"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nThe path allowance check in `GeneralUtility::isAllowedAbsPath()` performed a plain string prefix comparison without requiring a directory separator boundary, causing a path like `/var/www/html-other/secret.yaml` to be incorrectly accepted as valid when the project root was `/var/www/html`. Administrator users with access to the File Abstraction Layer were able to create new file storage definitions pointing to directories outside the project root, bypassing this path check.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Wolfgang Klinger for reporting this issue, and to TYPO3 core & security team member Oliver Hader for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-016","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 10.4.57"]},{"certainty":"source_listed","source_ids":["sr-26f7d9bdded8cdc8c9badd7b399dc99e"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nThe path allowance check in `GeneralUtility::isAllowedAbsPath()` performed a plain string prefix comparison without requiring a directory separator boundary, causing a path like `/var/www/html-other/secret.yaml` to be incorrectly accepted as valid when the project root was `/var/www/html`. Administrator users with access to the File Abstraction Layer were able to create new file storage definitions pointing to directories outside the project root, bypassing this path check.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Wolfgang Klinger for reporting this issue, and to TYPO3 core & security team member Oliver Hader for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-016","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.51"]},{"certainty":"source_listed","source_ids":["sr-26f7d9bdded8cdc8c9badd7b399dc99e"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nThe path allowance check in `GeneralUtility::isAllowedAbsPath()` performed a plain string prefix comparison without requiring a directory separator boundary, causing a path like `/var/www/html-other/secret.yaml` to be incorrectly accepted as valid when the project root was `/var/www/html`. Administrator users with access to the File Abstraction Layer were able to create new file storage definitions pointing to directories outside the project root, bypassing this path check.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Wolfgang Klinger for reporting this issue, and to TYPO3 core & security team member Oliver Hader for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-016","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0; fixed 12.4.46"]},{"certainty":"source_listed","source_ids":["sr-26f7d9bdded8cdc8c9badd7b399dc99e"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nThe path allowance check in `GeneralUtility::isAllowedAbsPath()` performed a plain string prefix comparison without requiring a directory separator boundary, causing a path like `/var/www/html-other/secret.yaml` to be incorrectly accepted as valid when the project root was `/var/www/html`. Administrator users with access to the File Abstraction Layer were able to create new file storage definitions pointing to directories outside the project root, bypassing this path check.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Wolfgang Klinger for reporting this issue, and to TYPO3 core & security team member Oliver Hader for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-016","public_affected_ranges":["ECOSYSTEM: introduced 13.0.0; fixed 13.4.31"]},{"certainty":"source_listed","source_ids":["sr-26f7d9bdded8cdc8c9badd7b399dc99e"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nThe path allowance check in `GeneralUtility::isAllowedAbsPath()` performed a plain string prefix comparison without requiring a directory separator boundary, causing a path like `/var/www/html-other/secret.yaml` to be incorrectly accepted as valid when the project root was `/var/www/html`. Administrator users with access to the File Abstraction Layer were able to create new file storage definitions pointing to directories outside the project root, bypassing this path check.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Wolfgang Klinger for reporting this issue, and to TYPO3 core & security team member Oliver Hader for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-016","public_affected_ranges":["ECOSYSTEM: introduced 14.0.0; fixed 14.3.3"]}],"null_published_at":"2026-11-02T20:21:10.267Z","source_updated_at":"2026-09-10T03:51:08.841Z","source_disclosed_at":"2026-06-12T19:09:04.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:20.441Z"},{"id":"NVI-00002792","kind":"vulnerability","title":"TYPO3 CMS has Broken Access Control in its File Abstraction Layer","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-jf56-v8jc-jcc5","CVE-2026-49738"],"plain_summary":"OSV carries this publisher advisory for typo3/cms-core, typo3/cms-core, typo3/cms-core, typo3/cms-core, typo3/cms-core. 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 10.4.57 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-26f7d9bdded8cdc8c9badd7b399dc99e"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 11.5.51 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-26f7d9bdded8cdc8c9badd7b399dc99e"],"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 12.4.46 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-26f7d9bdded8cdc8c9badd7b399dc99e"],"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 13.4.31 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-26f7d9bdded8cdc8c9badd7b399dc99e"],"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 14.3.3 for typo3/cms-core. Confirm the publisher’s latest guidance.","source_ids":["sr-26f7d9bdded8cdc8c9badd7b399dc99e"],"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-26f7d9bdded8cdc8c9badd7b399dc99e","url":"https://github.com/advisories/GHSA-jf56-v8jc-jcc5","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-jf56-v8jc-jcc5","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:20.441Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-26f7d9bdded8cdc8c9badd7b399dc99e"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nThe path allowance check in `GeneralUtility::isAllowedAbsPath()` performed a plain string prefix comparison without requiring a directory separator boundary, causing a path like `/var/www/html-other/secret.yaml` to be incorrectly accepted as valid when the project root was `/var/www/html`. Administrator users with access to the File Abstraction Layer were able to create new file storage definitions pointing to directories outside the project root, bypassing this path check.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Wolfgang Klinger for reporting this issue, and to TYPO3 core & security team member Oliver Hader for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-016","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 10.4.57"]},{"certainty":"source_listed","source_ids":["sr-26f7d9bdded8cdc8c9badd7b399dc99e"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nThe path allowance check in `GeneralUtility::isAllowedAbsPath()` performed a plain string prefix comparison without requiring a directory separator boundary, causing a path like `/var/www/html-other/secret.yaml` to be incorrectly accepted as valid when the project root was `/var/www/html`. Administrator users with access to the File Abstraction Layer were able to create new file storage definitions pointing to directories outside the project root, bypassing this path check.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Wolfgang Klinger for reporting this issue, and to TYPO3 core & security team member Oliver Hader for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-016","public_affected_ranges":["ECOSYSTEM: introduced 11.0.0; fixed 11.5.51"]},{"certainty":"source_listed","source_ids":["sr-26f7d9bdded8cdc8c9badd7b399dc99e"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nThe path allowance check in `GeneralUtility::isAllowedAbsPath()` performed a plain string prefix comparison without requiring a directory separator boundary, causing a path like `/var/www/html-other/secret.yaml` to be incorrectly accepted as valid when the project root was `/var/www/html`. Administrator users with access to the File Abstraction Layer were able to create new file storage definitions pointing to directories outside the project root, bypassing this path check.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Wolfgang Klinger for reporting this issue, and to TYPO3 core & security team member Oliver Hader for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-016","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0; fixed 12.4.46"]},{"certainty":"source_listed","source_ids":["sr-26f7d9bdded8cdc8c9badd7b399dc99e"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nThe path allowance check in `GeneralUtility::isAllowedAbsPath()` performed a plain string prefix comparison without requiring a directory separator boundary, causing a path like `/var/www/html-other/secret.yaml` to be incorrectly accepted as valid when the project root was `/var/www/html`. Administrator users with access to the File Abstraction Layer were able to create new file storage definitions pointing to directories outside the project root, bypassing this path check.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Wolfgang Klinger for reporting this issue, and to TYPO3 core & security team member Oliver Hader for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-016","public_affected_ranges":["ECOSYSTEM: introduced 13.0.0; fixed 13.4.31"]},{"certainty":"source_listed","source_ids":["sr-26f7d9bdded8cdc8c9badd7b399dc99e"],"technology":"typo3/cms-core","known_exclusions":[],"conditions_summary":"### Problem\nThe path allowance check in `GeneralUtility::isAllowedAbsPath()` performed a plain string prefix comparison without requiring a directory separator boundary, causing a path like `/var/www/html-other/secret.yaml` to be incorrectly accepted as valid when the project root was `/var/www/html`. Administrator users with access to the File Abstraction Layer were able to create new file storage definitions pointing to directories outside the project root, bypassing this path check.\n\n### Solution\nUpdate to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.\n\n### Credits\nTYPO3 CMS thanks Wolfgang Klinger for reporting this issue, and to TYPO3 core & security team member Oliver Hader for fixing it.\n\n### Resources\n* TYPO3-CORE-SA-2026-016","public_affected_ranges":["ECOSYSTEM: introduced 14.0.0; fixed 14.3.3"]}],"null_published_at":"2026-10-31T22:12:38.452Z","source_updated_at":"2026-09-10T03:51:08.841Z","source_disclosed_at":"2026-06-12T19:09:04.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:20.441Z"}],"next_cursor":null,"snapshot_revision":"42594"}