{"items":[{"id":"NVI-00005103","kind":"vulnerability","title":"Shopware: Admin API ACL Bypass in Order State Transition Endpoints","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-f8q6-3g5w-jjr6","CVE-2026-48014"],"plain_summary":"OSV carries this publisher advisory for shopware/platform, shopware/platform, shopware/core, shopware/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 6.7.10.1 for shopware/platform. Confirm the publisher’s latest guidance.","source_ids":["sr-821a6a690e51ffb98b9870370a544de4"],"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.6.10.18 for shopware/platform. Confirm the publisher’s latest guidance.","source_ids":["sr-821a6a690e51ffb98b9870370a544de4"],"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.7.10.1 for shopware/core. Confirm the publisher’s latest guidance.","source_ids":["sr-821a6a690e51ffb98b9870370a544de4"],"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.6.10.18 for shopware/core. Confirm the publisher’s latest guidance.","source_ids":["sr-821a6a690e51ffb98b9870370a544de4"],"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-801d6fd565806ffd5a763c730e404fcc"],"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-21T03:16:41.510Z","value":"6.5 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-6297eedf514dc75172bcbe5f7702d767"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.389%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.32981. Missing scores are unknown.","source_id":"sr-801d6fd565806ffd5a763c730e404fcc"}],"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-821a6a690e51ffb98b9870370a544de4","url":"https://github.com/advisories/GHSA-f8q6-3g5w-jjr6","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-f8q6-3g5w-jjr6","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.711Z"},{"id":"sr-6297eedf514dc75172bcbe5f7702d767","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-48014","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-48014","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:24:22.913Z"},{"id":"sr-801d6fd565806ffd5a763c730e404fcc","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-48014","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.379Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-821a6a690e51ffb98b9870370a544de4"],"technology":"shopware/platform","known_exclusions":[],"conditions_summary":"## Summary\nThis is a vertical authorization bypass in the Admin API affecting order state transition features (`/api/_action/order/{orderId}/state/{transition}` and similar transaction/delivery transition routes). The root cause is that the transition action routes do not declare required server-side ACL privileges, allowing low-privileged users to pass the authorization boundary. As a result, authenticated users without `order:update` can still change order states, causing real security impact such as operational integrity loss, automation workflow misuse, and fulfillment/settlement/support process disruption.\n\n## Description\nShopware’s permission model requires server-side enforcement independent of UI guards. However, the dedicated order-state transition action endpoints are missing ACL metadata, so accounts without regular order update privileges can still submit transition requests that are processed by the backend. In real reproduction, the same low-privileged account receives 403 on the normal order update API, while the transition action API succeeds with 200 and updates order state in the database. The key point is that reproduction is possible through direct API calls reg","public_affected_ranges":["ECOSYSTEM: introduced 6.7.0.0; fixed 6.7.10.1"]},{"certainty":"source_listed","source_ids":["sr-821a6a690e51ffb98b9870370a544de4"],"technology":"shopware/platform","known_exclusions":[],"conditions_summary":"## Summary\nThis is a vertical authorization bypass in the Admin API affecting order state transition features (`/api/_action/order/{orderId}/state/{transition}` and similar transaction/delivery transition routes). The root cause is that the transition action routes do not declare required server-side ACL privileges, allowing low-privileged users to pass the authorization boundary. As a result, authenticated users without `order:update` can still change order states, causing real security impact such as operational integrity loss, automation workflow misuse, and fulfillment/settlement/support process disruption.\n\n## Description\nShopware’s permission model requires server-side enforcement independent of UI guards. However, the dedicated order-state transition action endpoints are missing ACL metadata, so accounts without regular order update privileges can still submit transition requests that are processed by the backend. In real reproduction, the same low-privileged account receives 403 on the normal order update API, while the transition action API succeeds with 200 and updates order state in the database. The key point is that reproduction is possible through direct API calls reg","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.6.10.18"]},{"certainty":"source_listed","source_ids":["sr-821a6a690e51ffb98b9870370a544de4"],"technology":"shopware/core","known_exclusions":[],"conditions_summary":"## Summary\nThis is a vertical authorization bypass in the Admin API affecting order state transition features (`/api/_action/order/{orderId}/state/{transition}` and similar transaction/delivery transition routes). The root cause is that the transition action routes do not declare required server-side ACL privileges, allowing low-privileged users to pass the authorization boundary. As a result, authenticated users without `order:update` can still change order states, causing real security impact such as operational integrity loss, automation workflow misuse, and fulfillment/settlement/support process disruption.\n\n## Description\nShopware’s permission model requires server-side enforcement independent of UI guards. However, the dedicated order-state transition action endpoints are missing ACL metadata, so accounts without regular order update privileges can still submit transition requests that are processed by the backend. In real reproduction, the same low-privileged account receives 403 on the normal order update API, while the transition action API succeeds with 200 and updates order state in the database. The key point is that reproduction is possible through direct API calls reg","public_affected_ranges":["ECOSYSTEM: introduced 6.7.0.0; fixed 6.7.10.1"]},{"certainty":"source_listed","source_ids":["sr-821a6a690e51ffb98b9870370a544de4"],"technology":"shopware/core","known_exclusions":[],"conditions_summary":"## Summary\nThis is a vertical authorization bypass in the Admin API affecting order state transition features (`/api/_action/order/{orderId}/state/{transition}` and similar transaction/delivery transition routes). The root cause is that the transition action routes do not declare required server-side ACL privileges, allowing low-privileged users to pass the authorization boundary. As a result, authenticated users without `order:update` can still change order states, causing real security impact such as operational integrity loss, automation workflow misuse, and fulfillment/settlement/support process disruption.\n\n## Description\nShopware’s permission model requires server-side enforcement independent of UI guards. However, the dedicated order-state transition action endpoints are missing ACL metadata, so accounts without regular order update privileges can still submit transition requests that are processed by the backend. In real reproduction, the same low-privileged account receives 403 on the normal order update API, while the transition action API succeeds with 200 and updates order state in the database. The key point is that reproduction is possible through direct API calls reg","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.6.10.18"]}],"null_published_at":"2026-11-03T02:33:09.079Z","source_updated_at":"2026-09-10T03:50:49.441Z","source_disclosed_at":"2026-06-04T19:33:02.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:10.711Z"},{"id":"NVI-00005103","kind":"vulnerability","title":"Shopware: Admin API ACL Bypass in Order State Transition Endpoints","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-f8q6-3g5w-jjr6","CVE-2026-48014"],"plain_summary":"OSV carries this publisher advisory for shopware/platform, shopware/platform, shopware/core, shopware/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 6.7.10.1 for shopware/platform. Confirm the publisher’s latest guidance.","source_ids":["sr-821a6a690e51ffb98b9870370a544de4"],"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.6.10.18 for shopware/platform. Confirm the publisher’s latest guidance.","source_ids":["sr-821a6a690e51ffb98b9870370a544de4"],"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.7.10.1 for shopware/core. Confirm the publisher’s latest guidance.","source_ids":["sr-821a6a690e51ffb98b9870370a544de4"],"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.6.10.18 for shopware/core. Confirm the publisher’s latest guidance.","source_ids":["sr-821a6a690e51ffb98b9870370a544de4"],"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-6297eedf514dc75172bcbe5f7702d767"],"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-21T03:16:41.510Z","value":"6.5 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-6297eedf514dc75172bcbe5f7702d767"}],"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-821a6a690e51ffb98b9870370a544de4","url":"https://github.com/advisories/GHSA-f8q6-3g5w-jjr6","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-f8q6-3g5w-jjr6","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.711Z"},{"id":"sr-6297eedf514dc75172bcbe5f7702d767","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-48014","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-48014","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T07:24:22.913Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-821a6a690e51ffb98b9870370a544de4"],"technology":"shopware/platform","known_exclusions":[],"conditions_summary":"## Summary\nThis is a vertical authorization bypass in the Admin API affecting order state transition features (`/api/_action/order/{orderId}/state/{transition}` and similar transaction/delivery transition routes). The root cause is that the transition action routes do not declare required server-side ACL privileges, allowing low-privileged users to pass the authorization boundary. As a result, authenticated users without `order:update` can still change order states, causing real security impact such as operational integrity loss, automation workflow misuse, and fulfillment/settlement/support process disruption.\n\n## Description\nShopware’s permission model requires server-side enforcement independent of UI guards. However, the dedicated order-state transition action endpoints are missing ACL metadata, so accounts without regular order update privileges can still submit transition requests that are processed by the backend. In real reproduction, the same low-privileged account receives 403 on the normal order update API, while the transition action API succeeds with 200 and updates order state in the database. The key point is that reproduction is possible through direct API calls reg","public_affected_ranges":["ECOSYSTEM: introduced 6.7.0.0; fixed 6.7.10.1"]},{"certainty":"source_listed","source_ids":["sr-821a6a690e51ffb98b9870370a544de4"],"technology":"shopware/platform","known_exclusions":[],"conditions_summary":"## Summary\nThis is a vertical authorization bypass in the Admin API affecting order state transition features (`/api/_action/order/{orderId}/state/{transition}` and similar transaction/delivery transition routes). The root cause is that the transition action routes do not declare required server-side ACL privileges, allowing low-privileged users to pass the authorization boundary. As a result, authenticated users without `order:update` can still change order states, causing real security impact such as operational integrity loss, automation workflow misuse, and fulfillment/settlement/support process disruption.\n\n## Description\nShopware’s permission model requires server-side enforcement independent of UI guards. However, the dedicated order-state transition action endpoints are missing ACL metadata, so accounts without regular order update privileges can still submit transition requests that are processed by the backend. In real reproduction, the same low-privileged account receives 403 on the normal order update API, while the transition action API succeeds with 200 and updates order state in the database. The key point is that reproduction is possible through direct API calls reg","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.6.10.18"]},{"certainty":"source_listed","source_ids":["sr-821a6a690e51ffb98b9870370a544de4"],"technology":"shopware/core","known_exclusions":[],"conditions_summary":"## Summary\nThis is a vertical authorization bypass in the Admin API affecting order state transition features (`/api/_action/order/{orderId}/state/{transition}` and similar transaction/delivery transition routes). The root cause is that the transition action routes do not declare required server-side ACL privileges, allowing low-privileged users to pass the authorization boundary. As a result, authenticated users without `order:update` can still change order states, causing real security impact such as operational integrity loss, automation workflow misuse, and fulfillment/settlement/support process disruption.\n\n## Description\nShopware’s permission model requires server-side enforcement independent of UI guards. However, the dedicated order-state transition action endpoints are missing ACL metadata, so accounts without regular order update privileges can still submit transition requests that are processed by the backend. In real reproduction, the same low-privileged account receives 403 on the normal order update API, while the transition action API succeeds with 200 and updates order state in the database. The key point is that reproduction is possible through direct API calls reg","public_affected_ranges":["ECOSYSTEM: introduced 6.7.0.0; fixed 6.7.10.1"]},{"certainty":"source_listed","source_ids":["sr-821a6a690e51ffb98b9870370a544de4"],"technology":"shopware/core","known_exclusions":[],"conditions_summary":"## Summary\nThis is a vertical authorization bypass in the Admin API affecting order state transition features (`/api/_action/order/{orderId}/state/{transition}` and similar transaction/delivery transition routes). The root cause is that the transition action routes do not declare required server-side ACL privileges, allowing low-privileged users to pass the authorization boundary. As a result, authenticated users without `order:update` can still change order states, causing real security impact such as operational integrity loss, automation workflow misuse, and fulfillment/settlement/support process disruption.\n\n## Description\nShopware’s permission model requires server-side enforcement independent of UI guards. However, the dedicated order-state transition action endpoints are missing ACL metadata, so accounts without regular order update privileges can still submit transition requests that are processed by the backend. In real reproduction, the same low-privileged account receives 403 on the normal order update API, while the transition action API succeeds with 200 and updates order state in the database. The key point is that reproduction is possible through direct API calls reg","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.6.10.18"]}],"null_published_at":"2026-11-02T20:21:10.296Z","source_updated_at":"2026-09-10T03:50:49.441Z","source_disclosed_at":"2026-06-04T19:33:02.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:10.711Z"},{"id":"NVI-00005103","kind":"vulnerability","title":"Shopware: Admin API ACL Bypass in Order State Transition Endpoints","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-f8q6-3g5w-jjr6","CVE-2026-48014"],"plain_summary":"OSV carries this publisher advisory for shopware/platform, shopware/platform, shopware/core, shopware/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 6.7.10.1 for shopware/platform. Confirm the publisher’s latest guidance.","source_ids":["sr-821a6a690e51ffb98b9870370a544de4"],"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.6.10.18 for shopware/platform. Confirm the publisher’s latest guidance.","source_ids":["sr-821a6a690e51ffb98b9870370a544de4"],"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.7.10.1 for shopware/core. Confirm the publisher’s latest guidance.","source_ids":["sr-821a6a690e51ffb98b9870370a544de4"],"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.6.10.18 for shopware/core. Confirm the publisher’s latest guidance.","source_ids":["sr-821a6a690e51ffb98b9870370a544de4"],"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-821a6a690e51ffb98b9870370a544de4","url":"https://github.com/advisories/GHSA-f8q6-3g5w-jjr6","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-f8q6-3g5w-jjr6","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:10.711Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-821a6a690e51ffb98b9870370a544de4"],"technology":"shopware/platform","known_exclusions":[],"conditions_summary":"## Summary\nThis is a vertical authorization bypass in the Admin API affecting order state transition features (`/api/_action/order/{orderId}/state/{transition}` and similar transaction/delivery transition routes). The root cause is that the transition action routes do not declare required server-side ACL privileges, allowing low-privileged users to pass the authorization boundary. As a result, authenticated users without `order:update` can still change order states, causing real security impact such as operational integrity loss, automation workflow misuse, and fulfillment/settlement/support process disruption.\n\n## Description\nShopware’s permission model requires server-side enforcement independent of UI guards. However, the dedicated order-state transition action endpoints are missing ACL metadata, so accounts without regular order update privileges can still submit transition requests that are processed by the backend. In real reproduction, the same low-privileged account receives 403 on the normal order update API, while the transition action API succeeds with 200 and updates order state in the database. The key point is that reproduction is possible through direct API calls reg","public_affected_ranges":["ECOSYSTEM: introduced 6.7.0.0; fixed 6.7.10.1"]},{"certainty":"source_listed","source_ids":["sr-821a6a690e51ffb98b9870370a544de4"],"technology":"shopware/platform","known_exclusions":[],"conditions_summary":"## Summary\nThis is a vertical authorization bypass in the Admin API affecting order state transition features (`/api/_action/order/{orderId}/state/{transition}` and similar transaction/delivery transition routes). The root cause is that the transition action routes do not declare required server-side ACL privileges, allowing low-privileged users to pass the authorization boundary. As a result, authenticated users without `order:update` can still change order states, causing real security impact such as operational integrity loss, automation workflow misuse, and fulfillment/settlement/support process disruption.\n\n## Description\nShopware’s permission model requires server-side enforcement independent of UI guards. However, the dedicated order-state transition action endpoints are missing ACL metadata, so accounts without regular order update privileges can still submit transition requests that are processed by the backend. In real reproduction, the same low-privileged account receives 403 on the normal order update API, while the transition action API succeeds with 200 and updates order state in the database. The key point is that reproduction is possible through direct API calls reg","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.6.10.18"]},{"certainty":"source_listed","source_ids":["sr-821a6a690e51ffb98b9870370a544de4"],"technology":"shopware/core","known_exclusions":[],"conditions_summary":"## Summary\nThis is a vertical authorization bypass in the Admin API affecting order state transition features (`/api/_action/order/{orderId}/state/{transition}` and similar transaction/delivery transition routes). The root cause is that the transition action routes do not declare required server-side ACL privileges, allowing low-privileged users to pass the authorization boundary. As a result, authenticated users without `order:update` can still change order states, causing real security impact such as operational integrity loss, automation workflow misuse, and fulfillment/settlement/support process disruption.\n\n## Description\nShopware’s permission model requires server-side enforcement independent of UI guards. However, the dedicated order-state transition action endpoints are missing ACL metadata, so accounts without regular order update privileges can still submit transition requests that are processed by the backend. In real reproduction, the same low-privileged account receives 403 on the normal order update API, while the transition action API succeeds with 200 and updates order state in the database. The key point is that reproduction is possible through direct API calls reg","public_affected_ranges":["ECOSYSTEM: introduced 6.7.0.0; fixed 6.7.10.1"]},{"certainty":"source_listed","source_ids":["sr-821a6a690e51ffb98b9870370a544de4"],"technology":"shopware/core","known_exclusions":[],"conditions_summary":"## Summary\nThis is a vertical authorization bypass in the Admin API affecting order state transition features (`/api/_action/order/{orderId}/state/{transition}` and similar transaction/delivery transition routes). The root cause is that the transition action routes do not declare required server-side ACL privileges, allowing low-privileged users to pass the authorization boundary. As a result, authenticated users without `order:update` can still change order states, causing real security impact such as operational integrity loss, automation workflow misuse, and fulfillment/settlement/support process disruption.\n\n## Description\nShopware’s permission model requires server-side enforcement independent of UI guards. However, the dedicated order-state transition action endpoints are missing ACL metadata, so accounts without regular order update privileges can still submit transition requests that are processed by the backend. In real reproduction, the same low-privileged account receives 403 on the normal order update API, while the transition action API succeeds with 200 and updates order state in the database. The key point is that reproduction is possible through direct API calls reg","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.6.10.18"]}],"null_published_at":"2026-10-31T22:13:01.441Z","source_updated_at":"2026-09-10T03:50:49.441Z","source_disclosed_at":"2026-06-04T19:33:02.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:10.711Z"}],"next_cursor":null,"snapshot_revision":"42594"}