{"items":[{"id":"NVI-00005355","kind":"vulnerability","title":"Pimcore Platform - SQL Injection in DataObject composite index handling during class definition import/save","revision":4,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-r2f4-ff2p-xc64","CVE-2026-5394"],"plain_summary":"OSV carries this publisher advisory for pimcore/pimcore, pimcore/pimcore, pimcore/pimcore. 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 12.3.7 for pimcore/pimcore. Confirm the publisher’s latest guidance.","source_ids":["sr-8c476ff278b39ad42d0fbfe3c6cf2d83"],"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.17 for pimcore/pimcore. Confirm the publisher’s latest guidance.","source_ids":["sr-8c476ff278b39ad42d0fbfe3c6cf2d83"],"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 2026.1.3 for pimcore/pimcore. Confirm the publisher’s latest guidance.","source_ids":["sr-8c476ff278b39ad42d0fbfe3c6cf2d83"],"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-0c8c1bbb3cc16ebcfa9db8286bb6d6bf"],"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-17T10:58:57.263Z","value":"7 HIGH (4.0)","meaning":"help@fluidattacks.com severity; no combined Null risk score.","source_id":"sr-b1a594ba093ba2df33cf67a932d68cd8"},{"kind":"EPSS","as_of":"2026-11-01T12:00:16.000Z","value":"0.434%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.37692. Missing scores are unknown.","source_id":"sr-0c8c1bbb3cc16ebcfa9db8286bb6d6bf"}],"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-8c476ff278b39ad42d0fbfe3c6cf2d83","url":"https://github.com/advisories/GHSA-r2f4-ff2p-xc64","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-r2f4-ff2p-xc64","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.355Z"},{"id":"sr-b1a594ba093ba2df33cf67a932d68cd8","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-5394","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-5394","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:24:31.710Z"},{"id":"sr-0c8c1bbb3cc16ebcfa9db8286bb6d6bf","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-5394","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:28:32.284Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-8c476ff278b39ad42d0fbfe3c6cf2d83"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"My name is Oscar Uribe, Security Researcher at Fluid Attacks. I am reaching out because we have identified a security vulnerability in Pimcore 12.3.3 that we would like to report to you so we can coordinate a responsible disclosure together.\n\nAs part of our standard disclosure measures, we follow a timeline (outlined at https://fluidattacks.com/advisories/policy), which is aligned with ISO/IEC 29147:2018 and ISO/IEC 30111:2019. In short, the timeline works as follows: we ask for acknowledgment of the report within a few days of your first accessing it, and from there, we are happy to coordinate a joint disclosure date with you, typically within 90 days of the initial discovery. This gives your team reasonable time to assess, develop, and release a fix.\n\nWe have reserved the CVE ID **\"CVE-2026-5394\"** for this issue, and the advisory will eventually be published at https://fluidattacks.com/advisories/dragons. We are committed to coordinating the timing of that publication with you.\n\nPlease feel free to reach out if you have any questions about the report, the process, or the timeline. We are glad to work with you on this.\n\n## Descriptio","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0-RC1; fixed 12.3.7"]},{"certainty":"source_listed","source_ids":["sr-8c476ff278b39ad42d0fbfe3c6cf2d83"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"My name is Oscar Uribe, Security Researcher at Fluid Attacks. I am reaching out because we have identified a security vulnerability in Pimcore 12.3.3 that we would like to report to you so we can coordinate a responsible disclosure together.\n\nAs part of our standard disclosure measures, we follow a timeline (outlined at https://fluidattacks.com/advisories/policy), which is aligned with ISO/IEC 29147:2018 and ISO/IEC 30111:2019. In short, the timeline works as follows: we ask for acknowledgment of the report within a few days of your first accessing it, and from there, we are happy to coordinate a joint disclosure date with you, typically within 90 days of the initial discovery. This gives your team reasonable time to assess, develop, and release a fix.\n\nWe have reserved the CVE ID **\"CVE-2026-5394\"** for this issue, and the advisory will eventually be published at https://fluidattacks.com/advisories/dragons. We are committed to coordinating the timing of that publication with you.\n\nPlease feel free to reach out if you have any questions about the report, the process, or the timeline. We are glad to work with you on this.\n\n## Descriptio","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 11.5.17"]},{"certainty":"source_listed","source_ids":["sr-8c476ff278b39ad42d0fbfe3c6cf2d83"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"My name is Oscar Uribe, Security Researcher at Fluid Attacks. I am reaching out because we have identified a security vulnerability in Pimcore 12.3.3 that we would like to report to you so we can coordinate a responsible disclosure together.\n\nAs part of our standard disclosure measures, we follow a timeline (outlined at https://fluidattacks.com/advisories/policy), which is aligned with ISO/IEC 29147:2018 and ISO/IEC 30111:2019. In short, the timeline works as follows: we ask for acknowledgment of the report within a few days of your first accessing it, and from there, we are happy to coordinate a joint disclosure date with you, typically within 90 days of the initial discovery. This gives your team reasonable time to assess, develop, and release a fix.\n\nWe have reserved the CVE ID **\"CVE-2026-5394\"** for this issue, and the advisory will eventually be published at https://fluidattacks.com/advisories/dragons. We are committed to coordinating the timing of that publication with you.\n\nPlease feel free to reach out if you have any questions about the report, the process, or the timeline. We are glad to work with you on this.\n\n## Descriptio","public_affected_ranges":["ECOSYSTEM: introduced 2026.1.0; fixed 2026.1.3"]}],"null_published_at":"2026-11-06T15:18:17.685Z","source_updated_at":"2026-08-29T11:55:52.524Z","source_disclosed_at":"2026-05-28T20:47:10.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.355Z"},{"id":"NVI-00005355","kind":"vulnerability","title":"Pimcore Platform - SQL Injection in DataObject composite index handling during class definition import/save","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-r2f4-ff2p-xc64","CVE-2026-5394"],"plain_summary":"OSV carries this publisher advisory for pimcore/pimcore, pimcore/pimcore, pimcore/pimcore. 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 12.3.7 for pimcore/pimcore. Confirm the publisher’s latest guidance.","source_ids":["sr-8c476ff278b39ad42d0fbfe3c6cf2d83"],"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.17 for pimcore/pimcore. Confirm the publisher’s latest guidance.","source_ids":["sr-8c476ff278b39ad42d0fbfe3c6cf2d83"],"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 2026.1.3 for pimcore/pimcore. Confirm the publisher’s latest guidance.","source_ids":["sr-8c476ff278b39ad42d0fbfe3c6cf2d83"],"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-0c8c1bbb3cc16ebcfa9db8286bb6d6bf"],"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-01T12:00:16.000Z","value":"0.434%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.37692. Missing scores are unknown.","source_id":"sr-0c8c1bbb3cc16ebcfa9db8286bb6d6bf"}],"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-8c476ff278b39ad42d0fbfe3c6cf2d83","url":"https://github.com/advisories/GHSA-r2f4-ff2p-xc64","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-r2f4-ff2p-xc64","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.355Z"},{"id":"sr-0c8c1bbb3cc16ebcfa9db8286bb6d6bf","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-5394","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:28:32.284Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-8c476ff278b39ad42d0fbfe3c6cf2d83"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"My name is Oscar Uribe, Security Researcher at Fluid Attacks. I am reaching out because we have identified a security vulnerability in Pimcore 12.3.3 that we would like to report to you so we can coordinate a responsible disclosure together.\n\nAs part of our standard disclosure measures, we follow a timeline (outlined at https://fluidattacks.com/advisories/policy), which is aligned with ISO/IEC 29147:2018 and ISO/IEC 30111:2019. In short, the timeline works as follows: we ask for acknowledgment of the report within a few days of your first accessing it, and from there, we are happy to coordinate a joint disclosure date with you, typically within 90 days of the initial discovery. This gives your team reasonable time to assess, develop, and release a fix.\n\nWe have reserved the CVE ID **\"CVE-2026-5394\"** for this issue, and the advisory will eventually be published at https://fluidattacks.com/advisories/dragons. We are committed to coordinating the timing of that publication with you.\n\nPlease feel free to reach out if you have any questions about the report, the process, or the timeline. We are glad to work with you on this.\n\n## Descriptio","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0-RC1; fixed 12.3.7"]},{"certainty":"source_listed","source_ids":["sr-8c476ff278b39ad42d0fbfe3c6cf2d83"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"My name is Oscar Uribe, Security Researcher at Fluid Attacks. I am reaching out because we have identified a security vulnerability in Pimcore 12.3.3 that we would like to report to you so we can coordinate a responsible disclosure together.\n\nAs part of our standard disclosure measures, we follow a timeline (outlined at https://fluidattacks.com/advisories/policy), which is aligned with ISO/IEC 29147:2018 and ISO/IEC 30111:2019. In short, the timeline works as follows: we ask for acknowledgment of the report within a few days of your first accessing it, and from there, we are happy to coordinate a joint disclosure date with you, typically within 90 days of the initial discovery. This gives your team reasonable time to assess, develop, and release a fix.\n\nWe have reserved the CVE ID **\"CVE-2026-5394\"** for this issue, and the advisory will eventually be published at https://fluidattacks.com/advisories/dragons. We are committed to coordinating the timing of that publication with you.\n\nPlease feel free to reach out if you have any questions about the report, the process, or the timeline. We are glad to work with you on this.\n\n## Descriptio","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 11.5.17"]},{"certainty":"source_listed","source_ids":["sr-8c476ff278b39ad42d0fbfe3c6cf2d83"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"My name is Oscar Uribe, Security Researcher at Fluid Attacks. I am reaching out because we have identified a security vulnerability in Pimcore 12.3.3 that we would like to report to you so we can coordinate a responsible disclosure together.\n\nAs part of our standard disclosure measures, we follow a timeline (outlined at https://fluidattacks.com/advisories/policy), which is aligned with ISO/IEC 29147:2018 and ISO/IEC 30111:2019. In short, the timeline works as follows: we ask for acknowledgment of the report within a few days of your first accessing it, and from there, we are happy to coordinate a joint disclosure date with you, typically within 90 days of the initial discovery. This gives your team reasonable time to assess, develop, and release a fix.\n\nWe have reserved the CVE ID **\"CVE-2026-5394\"** for this issue, and the advisory will eventually be published at https://fluidattacks.com/advisories/dragons. We are committed to coordinating the timing of that publication with you.\n\nPlease feel free to reach out if you have any questions about the report, the process, or the timeline. We are glad to work with you on this.\n\n## Descriptio","public_affected_ranges":["ECOSYSTEM: introduced 2026.1.0; fixed 2026.1.3"]}],"null_published_at":"2026-11-03T17:49:15.042Z","source_updated_at":"2026-08-29T11:55:52.524Z","source_disclosed_at":"2026-05-28T20:47:10.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.355Z"},{"id":"NVI-00005355","kind":"vulnerability","title":"Pimcore Platform - SQL Injection in DataObject composite index handling during class definition import/save","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-r2f4-ff2p-xc64","CVE-2026-5394"],"plain_summary":"OSV carries this publisher advisory for pimcore/pimcore, pimcore/pimcore, pimcore/pimcore. 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 12.3.7 for pimcore/pimcore. Confirm the publisher’s latest guidance.","source_ids":["sr-8c476ff278b39ad42d0fbfe3c6cf2d83"],"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.17 for pimcore/pimcore. Confirm the publisher’s latest guidance.","source_ids":["sr-8c476ff278b39ad42d0fbfe3c6cf2d83"],"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 2026.1.3 for pimcore/pimcore. Confirm the publisher’s latest guidance.","source_ids":["sr-8c476ff278b39ad42d0fbfe3c6cf2d83"],"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-1091b5e4f88e7b9274e011eec4379386"],"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.434%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.37699. Missing scores are unknown.","source_id":"sr-1091b5e4f88e7b9274e011eec4379386"}],"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-8c476ff278b39ad42d0fbfe3c6cf2d83","url":"https://github.com/advisories/GHSA-r2f4-ff2p-xc64","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-r2f4-ff2p-xc64","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:41.355Z"},{"id":"sr-1091b5e4f88e7b9274e011eec4379386","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-5394","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.383Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-8c476ff278b39ad42d0fbfe3c6cf2d83"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"My name is Oscar Uribe, Security Researcher at Fluid Attacks. I am reaching out because we have identified a security vulnerability in Pimcore 12.3.3 that we would like to report to you so we can coordinate a responsible disclosure together.\n\nAs part of our standard disclosure measures, we follow a timeline (outlined at https://fluidattacks.com/advisories/policy), which is aligned with ISO/IEC 29147:2018 and ISO/IEC 30111:2019. In short, the timeline works as follows: we ask for acknowledgment of the report within a few days of your first accessing it, and from there, we are happy to coordinate a joint disclosure date with you, typically within 90 days of the initial discovery. This gives your team reasonable time to assess, develop, and release a fix.\n\nWe have reserved the CVE ID **\"CVE-2026-5394\"** for this issue, and the advisory will eventually be published at https://fluidattacks.com/advisories/dragons. We are committed to coordinating the timing of that publication with you.\n\nPlease feel free to reach out if you have any questions about the report, the process, or the timeline. We are glad to work with you on this.\n\n## Descriptio","public_affected_ranges":["ECOSYSTEM: introduced 12.0.0-RC1; fixed 12.3.7"]},{"certainty":"source_listed","source_ids":["sr-8c476ff278b39ad42d0fbfe3c6cf2d83"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"My name is Oscar Uribe, Security Researcher at Fluid Attacks. I am reaching out because we have identified a security vulnerability in Pimcore 12.3.3 that we would like to report to you so we can coordinate a responsible disclosure together.\n\nAs part of our standard disclosure measures, we follow a timeline (outlined at https://fluidattacks.com/advisories/policy), which is aligned with ISO/IEC 29147:2018 and ISO/IEC 30111:2019. In short, the timeline works as follows: we ask for acknowledgment of the report within a few days of your first accessing it, and from there, we are happy to coordinate a joint disclosure date with you, typically within 90 days of the initial discovery. This gives your team reasonable time to assess, develop, and release a fix.\n\nWe have reserved the CVE ID **\"CVE-2026-5394\"** for this issue, and the advisory will eventually be published at https://fluidattacks.com/advisories/dragons. We are committed to coordinating the timing of that publication with you.\n\nPlease feel free to reach out if you have any questions about the report, the process, or the timeline. We are glad to work with you on this.\n\n## Descriptio","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 11.5.17"]},{"certainty":"source_listed","source_ids":["sr-8c476ff278b39ad42d0fbfe3c6cf2d83"],"technology":"pimcore/pimcore","known_exclusions":[],"conditions_summary":"My name is Oscar Uribe, Security Researcher at Fluid Attacks. I am reaching out because we have identified a security vulnerability in Pimcore 12.3.3 that we would like to report to you so we can coordinate a responsible disclosure together.\n\nAs part of our standard disclosure measures, we follow a timeline (outlined at https://fluidattacks.com/advisories/policy), which is aligned with ISO/IEC 29147:2018 and ISO/IEC 30111:2019. In short, the timeline works as follows: we ask for acknowledgment of the report within a few days of your first accessing it, and from there, we are happy to coordinate a joint disclosure date with you, typically within 90 days of the initial discovery. This gives your team reasonable time to assess, develop, and release a fix.\n\nWe have reserved the CVE ID **\"CVE-2026-5394\"** for this issue, and the advisory will eventually be published at https://fluidattacks.com/advisories/dragons. We are committed to coordinating the timing of that publication with you.\n\nPlease feel free to reach out if you have any questions about the report, the process, or the timeline. We are glad to work with you on this.\n\n## Descriptio","public_affected_ranges":["ECOSYSTEM: introduced 2026.1.0; fixed 2026.1.3"]}],"null_published_at":"2026-10-31T22:13:48.406Z","source_updated_at":"2026-08-29T11:55:52.524Z","source_disclosed_at":"2026-05-28T20:47:10.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.355Z"}],"next_cursor":null,"snapshot_revision":"42594"}