{"items":[{"id":"NVI-00004333","kind":"vulnerability","title":"Shopware: Privilege Escalation via Sync API Integration Admin Flag Bypass","revision":4,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-gv8p-48fr-4fxg","CVE-2026-48008"],"plain_summary":"GitHub lists this reviewed advisory for shopware/platform, shopware/platform, shopware/core, shopware/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-32a44be4c717698c98067a7110983586"],"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 6.7.10.1 for shopware/platform. Confirm the publisher’s latest guidance.","source_ids":["sr-6278f281f4dd8a709451e0d284c8a839"],"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-6278f281f4dd8a709451e0d284c8a839"],"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-6278f281f4dd8a709451e0d284c8a839"],"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-6278f281f4dd8a709451e0d284c8a839"],"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-06-04T19:23:34.000Z","value":"6.5 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-1198c03687886538726f3207927dcf18"},{"kind":"EPSS","as_of":"2026-11-01T12:00:16.000Z","value":"0.472%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.40826. Missing scores are unknown.","source_id":"sr-32a44be4c717698c98067a7110983586"}],"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-1198c03687886538726f3207927dcf18","url":"https://github.com/advisories/GHSA-gv8p-48fr-4fxg","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-gv8p-48fr-4fxg","publisher":"GitHub Advisory Database","observed_at":"2026-11-07T00:53:06.181Z"},{"id":"sr-6278f281f4dd8a709451e0d284c8a839","url":"https://github.com/advisories/GHSA-gv8p-48fr-4fxg","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-gv8p-48fr-4fxg","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:20.422Z"},{"id":"sr-32a44be4c717698c98067a7110983586","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-48008","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:28:32.280Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-1198c03687886538726f3207927dcf18"],"technology":"shopware/platform","known_exclusions":[],"conditions_summary":"## Summary\n\nA non-admin API user with `integration:create` ACL privilege can escalate to full administrator by creating an integration with `admin: true` through the Sync API (`POST /api/_action/sync`). The regular integration endpoint (`POST /api/integration`) correctly blocks this, but the Sync API bypasses the controller-level check by writing directly through the DAL EntityWriter. The `integration` entity definition lacks `WriteProtection`, and the `admin` field has no field-level restriction flag.\n\n**OWASP:** A01:2021 — Broken Access Control\n\n## Root Cause\n\n`IntegrationController::upsertIntegration()` checks `$source->isAdmin()` before allowing the `admin` field to be set. However, `SyncController::sync()` routes writes through `SyncService → EntityWriter`, which only applies:\n\n1. `AclWriteValidator` — checks entity-level ACL (`integration:create` is sufficient)\n2. `EntityProtectionValidator` — checks `WriteProtection` on entity definitions, but `IntegrationDefinition` has none\n\nThe `admin` field in `IntegrationDefinition` is a plain `BoolField` with no `WriteProtection` or special flag. The Sync API writes it without restriction.\n\n**Vulnerable code path:**\n- `src/Core/Framewo","public_affected_ranges":[">= 6.7.0.0, < 6.7.10.1"]},{"certainty":"source_listed","source_ids":["sr-1198c03687886538726f3207927dcf18"],"technology":"shopware/platform","known_exclusions":[],"conditions_summary":"## Summary\n\nA non-admin API user with `integration:create` ACL privilege can escalate to full administrator by creating an integration with `admin: true` through the Sync API (`POST /api/_action/sync`). The regular integration endpoint (`POST /api/integration`) correctly blocks this, but the Sync API bypasses the controller-level check by writing directly through the DAL EntityWriter. The `integration` entity definition lacks `WriteProtection`, and the `admin` field has no field-level restriction flag.\n\n**OWASP:** A01:2021 — Broken Access Control\n\n## Root Cause\n\n`IntegrationController::upsertIntegration()` checks `$source->isAdmin()` before allowing the `admin` field to be set. However, `SyncController::sync()` routes writes through `SyncService → EntityWriter`, which only applies:\n\n1. `AclWriteValidator` — checks entity-level ACL (`integration:create` is sufficient)\n2. `EntityProtectionValidator` — checks `WriteProtection` on entity definitions, but `IntegrationDefinition` has none\n\nThe `admin` field in `IntegrationDefinition` is a plain `BoolField` with no `WriteProtection` or special flag. The Sync API writes it without restriction.\n\n**Vulnerable code path:**\n- `src/Core/Framewo","public_affected_ranges":["< 6.6.10.18"]},{"certainty":"source_listed","source_ids":["sr-1198c03687886538726f3207927dcf18"],"technology":"shopware/core","known_exclusions":[],"conditions_summary":"## Summary\n\nA non-admin API user with `integration:create` ACL privilege can escalate to full administrator by creating an integration with `admin: true` through the Sync API (`POST /api/_action/sync`). The regular integration endpoint (`POST /api/integration`) correctly blocks this, but the Sync API bypasses the controller-level check by writing directly through the DAL EntityWriter. The `integration` entity definition lacks `WriteProtection`, and the `admin` field has no field-level restriction flag.\n\n**OWASP:** A01:2021 — Broken Access Control\n\n## Root Cause\n\n`IntegrationController::upsertIntegration()` checks `$source->isAdmin()` before allowing the `admin` field to be set. However, `SyncController::sync()` routes writes through `SyncService → EntityWriter`, which only applies:\n\n1. `AclWriteValidator` — checks entity-level ACL (`integration:create` is sufficient)\n2. `EntityProtectionValidator` — checks `WriteProtection` on entity definitions, but `IntegrationDefinition` has none\n\nThe `admin` field in `IntegrationDefinition` is a plain `BoolField` with no `WriteProtection` or special flag. The Sync API writes it without restriction.\n\n**Vulnerable code path:**\n- `src/Core/Framewo","public_affected_ranges":[">= 6.7.0.0, < 6.7.10.1"]},{"certainty":"source_listed","source_ids":["sr-1198c03687886538726f3207927dcf18"],"technology":"shopware/core","known_exclusions":[],"conditions_summary":"## Summary\n\nA non-admin API user with `integration:create` ACL privilege can escalate to full administrator by creating an integration with `admin: true` through the Sync API (`POST /api/_action/sync`). The regular integration endpoint (`POST /api/integration`) correctly blocks this, but the Sync API bypasses the controller-level check by writing directly through the DAL EntityWriter. The `integration` entity definition lacks `WriteProtection`, and the `admin` field has no field-level restriction flag.\n\n**OWASP:** A01:2021 — Broken Access Control\n\n## Root Cause\n\n`IntegrationController::upsertIntegration()` checks `$source->isAdmin()` before allowing the `admin` field to be set. However, `SyncController::sync()` routes writes through `SyncService → EntityWriter`, which only applies:\n\n1. `AclWriteValidator` — checks entity-level ACL (`integration:create` is sufficient)\n2. `EntityProtectionValidator` — checks `WriteProtection` on entity definitions, but `IntegrationDefinition` has none\n\nThe `admin` field in `IntegrationDefinition` is a plain `BoolField` with no `WriteProtection` or special flag. The Sync API writes it without restriction.\n\n**Vulnerable code path:**\n- `src/Core/Framewo","public_affected_ranges":["< 6.6.10.18"]},{"certainty":"source_listed","source_ids":["sr-6278f281f4dd8a709451e0d284c8a839"],"technology":"shopware/platform","known_exclusions":[],"conditions_summary":"## Summary\n\nA non-admin API user with `integration:create` ACL privilege can escalate to full administrator by creating an integration with `admin: true` through the Sync API (`POST /api/_action/sync`). The regular integration endpoint (`POST /api/integration`) correctly blocks this, but the Sync API bypasses the controller-level check by writing directly through the DAL EntityWriter. The `integration` entity definition lacks `WriteProtection`, and the `admin` field has no field-level restriction flag.\n\n**OWASP:** A01:2021 — Broken Access Control\n\n## Root Cause\n\n`IntegrationController::upsertIntegration()` checks `$source->isAdmin()` before allowing the `admin` field to be set. However, `SyncController::sync()` routes writes through `SyncService → EntityWriter`, which only applies:\n\n1. `AclWriteValidator` — checks entity-level ACL (`integration:create` is sufficient)\n2. `EntityProtectionValidator` — checks `WriteProtection` on entity definitions, but `IntegrationDefinition` has none\n\nThe `admin` field in `IntegrationDefinition` is a plain `BoolField` with no `WriteProtection` or special flag. The Sync API writes it without restriction.\n\n**Vulnerable code path:**\n- `src/Core/Framewo","public_affected_ranges":["ECOSYSTEM: introduced 6.7.0.0; fixed 6.7.10.1"]},{"certainty":"source_listed","source_ids":["sr-6278f281f4dd8a709451e0d284c8a839"],"technology":"shopware/platform","known_exclusions":[],"conditions_summary":"## Summary\n\nA non-admin API user with `integration:create` ACL privilege can escalate to full administrator by creating an integration with `admin: true` through the Sync API (`POST /api/_action/sync`). The regular integration endpoint (`POST /api/integration`) correctly blocks this, but the Sync API bypasses the controller-level check by writing directly through the DAL EntityWriter. The `integration` entity definition lacks `WriteProtection`, and the `admin` field has no field-level restriction flag.\n\n**OWASP:** A01:2021 — Broken Access Control\n\n## Root Cause\n\n`IntegrationController::upsertIntegration()` checks `$source->isAdmin()` before allowing the `admin` field to be set. However, `SyncController::sync()` routes writes through `SyncService → EntityWriter`, which only applies:\n\n1. `AclWriteValidator` — checks entity-level ACL (`integration:create` is sufficient)\n2. `EntityProtectionValidator` — checks `WriteProtection` on entity definitions, but `IntegrationDefinition` has none\n\nThe `admin` field in `IntegrationDefinition` is a plain `BoolField` with no `WriteProtection` or special flag. The Sync API writes it without restriction.\n\n**Vulnerable code path:**\n- `src/Core/Framewo","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.6.10.18"]},{"certainty":"source_listed","source_ids":["sr-6278f281f4dd8a709451e0d284c8a839"],"technology":"shopware/core","known_exclusions":[],"conditions_summary":"## Summary\n\nA non-admin API user with `integration:create` ACL privilege can escalate to full administrator by creating an integration with `admin: true` through the Sync API (`POST /api/_action/sync`). The regular integration endpoint (`POST /api/integration`) correctly blocks this, but the Sync API bypasses the controller-level check by writing directly through the DAL EntityWriter. The `integration` entity definition lacks `WriteProtection`, and the `admin` field has no field-level restriction flag.\n\n**OWASP:** A01:2021 — Broken Access Control\n\n## Root Cause\n\n`IntegrationController::upsertIntegration()` checks `$source->isAdmin()` before allowing the `admin` field to be set. However, `SyncController::sync()` routes writes through `SyncService → EntityWriter`, which only applies:\n\n1. `AclWriteValidator` — checks entity-level ACL (`integration:create` is sufficient)\n2. `EntityProtectionValidator` — checks `WriteProtection` on entity definitions, but `IntegrationDefinition` has none\n\nThe `admin` field in `IntegrationDefinition` is a plain `BoolField` with no `WriteProtection` or special flag. The Sync API writes it without restriction.\n\n**Vulnerable code path:**\n- `src/Core/Framewo","public_affected_ranges":["ECOSYSTEM: introduced 6.7.0.0; fixed 6.7.10.1"]},{"certainty":"source_listed","source_ids":["sr-6278f281f4dd8a709451e0d284c8a839"],"technology":"shopware/core","known_exclusions":[],"conditions_summary":"## Summary\n\nA non-admin API user with `integration:create` ACL privilege can escalate to full administrator by creating an integration with `admin: true` through the Sync API (`POST /api/_action/sync`). The regular integration endpoint (`POST /api/integration`) correctly blocks this, but the Sync API bypasses the controller-level check by writing directly through the DAL EntityWriter. The `integration` entity definition lacks `WriteProtection`, and the `admin` field has no field-level restriction flag.\n\n**OWASP:** A01:2021 — Broken Access Control\n\n## Root Cause\n\n`IntegrationController::upsertIntegration()` checks `$source->isAdmin()` before allowing the `admin` field to be set. However, `SyncController::sync()` routes writes through `SyncService → EntityWriter`, which only applies:\n\n1. `AclWriteValidator` — checks entity-level ACL (`integration:create` is sufficient)\n2. `EntityProtectionValidator` — checks `WriteProtection` on entity definitions, but `IntegrationDefinition` has none\n\nThe `admin` field in `IntegrationDefinition` is a plain `BoolField` with no `WriteProtection` or special flag. The Sync API writes it without restriction.\n\n**Vulnerable code path:**\n- `src/Core/Framewo","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.6.10.18"]}],"null_published_at":"2026-11-07T18:43:12.116Z","source_updated_at":"2026-06-04T19:23:34.000Z","source_disclosed_at":"2026-06-04T19:23:33.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:20.422Z"},{"id":"NVI-00004333","kind":"vulnerability","title":"Shopware: Privilege Escalation via Sync API Integration Admin Flag Bypass","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-gv8p-48fr-4fxg","CVE-2026-48008"],"plain_summary":"GitHub lists this reviewed advisory for shopware/platform, shopware/platform, shopware/core, shopware/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-3d1365f21aea5bf68e7b9c8c57d5e90a"],"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 6.7.10.1 for shopware/platform. Confirm the publisher’s latest guidance.","source_ids":["sr-6278f281f4dd8a709451e0d284c8a839"],"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-6278f281f4dd8a709451e0d284c8a839"],"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-6278f281f4dd8a709451e0d284c8a839"],"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-6278f281f4dd8a709451e0d284c8a839"],"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-06-04T19:23:34.000Z","value":"6.5 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-1198c03687886538726f3207927dcf18"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.472%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.40833. Missing scores are unknown.","source_id":"sr-3d1365f21aea5bf68e7b9c8c57d5e90a"}],"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-1198c03687886538726f3207927dcf18","url":"https://github.com/advisories/GHSA-gv8p-48fr-4fxg","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-gv8p-48fr-4fxg","publisher":"GitHub Advisory Database","observed_at":"2026-11-07T00:53:06.181Z"},{"id":"sr-6278f281f4dd8a709451e0d284c8a839","url":"https://github.com/advisories/GHSA-gv8p-48fr-4fxg","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-gv8p-48fr-4fxg","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:20.422Z"},{"id":"sr-3d1365f21aea5bf68e7b9c8c57d5e90a","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-48008","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.379Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-1198c03687886538726f3207927dcf18"],"technology":"shopware/platform","known_exclusions":[],"conditions_summary":"## Summary\n\nA non-admin API user with `integration:create` ACL privilege can escalate to full administrator by creating an integration with `admin: true` through the Sync API (`POST /api/_action/sync`). The regular integration endpoint (`POST /api/integration`) correctly blocks this, but the Sync API bypasses the controller-level check by writing directly through the DAL EntityWriter. The `integration` entity definition lacks `WriteProtection`, and the `admin` field has no field-level restriction flag.\n\n**OWASP:** A01:2021 — Broken Access Control\n\n## Root Cause\n\n`IntegrationController::upsertIntegration()` checks `$source->isAdmin()` before allowing the `admin` field to be set. However, `SyncController::sync()` routes writes through `SyncService → EntityWriter`, which only applies:\n\n1. `AclWriteValidator` — checks entity-level ACL (`integration:create` is sufficient)\n2. `EntityProtectionValidator` — checks `WriteProtection` on entity definitions, but `IntegrationDefinition` has none\n\nThe `admin` field in `IntegrationDefinition` is a plain `BoolField` with no `WriteProtection` or special flag. The Sync API writes it without restriction.\n\n**Vulnerable code path:**\n- `src/Core/Framewo","public_affected_ranges":[">= 6.7.0.0, < 6.7.10.1"]},{"certainty":"source_listed","source_ids":["sr-1198c03687886538726f3207927dcf18"],"technology":"shopware/platform","known_exclusions":[],"conditions_summary":"## Summary\n\nA non-admin API user with `integration:create` ACL privilege can escalate to full administrator by creating an integration with `admin: true` through the Sync API (`POST /api/_action/sync`). The regular integration endpoint (`POST /api/integration`) correctly blocks this, but the Sync API bypasses the controller-level check by writing directly through the DAL EntityWriter. The `integration` entity definition lacks `WriteProtection`, and the `admin` field has no field-level restriction flag.\n\n**OWASP:** A01:2021 — Broken Access Control\n\n## Root Cause\n\n`IntegrationController::upsertIntegration()` checks `$source->isAdmin()` before allowing the `admin` field to be set. However, `SyncController::sync()` routes writes through `SyncService → EntityWriter`, which only applies:\n\n1. `AclWriteValidator` — checks entity-level ACL (`integration:create` is sufficient)\n2. `EntityProtectionValidator` — checks `WriteProtection` on entity definitions, but `IntegrationDefinition` has none\n\nThe `admin` field in `IntegrationDefinition` is a plain `BoolField` with no `WriteProtection` or special flag. The Sync API writes it without restriction.\n\n**Vulnerable code path:**\n- `src/Core/Framewo","public_affected_ranges":["< 6.6.10.18"]},{"certainty":"source_listed","source_ids":["sr-1198c03687886538726f3207927dcf18"],"technology":"shopware/core","known_exclusions":[],"conditions_summary":"## Summary\n\nA non-admin API user with `integration:create` ACL privilege can escalate to full administrator by creating an integration with `admin: true` through the Sync API (`POST /api/_action/sync`). The regular integration endpoint (`POST /api/integration`) correctly blocks this, but the Sync API bypasses the controller-level check by writing directly through the DAL EntityWriter. The `integration` entity definition lacks `WriteProtection`, and the `admin` field has no field-level restriction flag.\n\n**OWASP:** A01:2021 — Broken Access Control\n\n## Root Cause\n\n`IntegrationController::upsertIntegration()` checks `$source->isAdmin()` before allowing the `admin` field to be set. However, `SyncController::sync()` routes writes through `SyncService → EntityWriter`, which only applies:\n\n1. `AclWriteValidator` — checks entity-level ACL (`integration:create` is sufficient)\n2. `EntityProtectionValidator` — checks `WriteProtection` on entity definitions, but `IntegrationDefinition` has none\n\nThe `admin` field in `IntegrationDefinition` is a plain `BoolField` with no `WriteProtection` or special flag. The Sync API writes it without restriction.\n\n**Vulnerable code path:**\n- `src/Core/Framewo","public_affected_ranges":[">= 6.7.0.0, < 6.7.10.1"]},{"certainty":"source_listed","source_ids":["sr-1198c03687886538726f3207927dcf18"],"technology":"shopware/core","known_exclusions":[],"conditions_summary":"## Summary\n\nA non-admin API user with `integration:create` ACL privilege can escalate to full administrator by creating an integration with `admin: true` through the Sync API (`POST /api/_action/sync`). The regular integration endpoint (`POST /api/integration`) correctly blocks this, but the Sync API bypasses the controller-level check by writing directly through the DAL EntityWriter. The `integration` entity definition lacks `WriteProtection`, and the `admin` field has no field-level restriction flag.\n\n**OWASP:** A01:2021 — Broken Access Control\n\n## Root Cause\n\n`IntegrationController::upsertIntegration()` checks `$source->isAdmin()` before allowing the `admin` field to be set. However, `SyncController::sync()` routes writes through `SyncService → EntityWriter`, which only applies:\n\n1. `AclWriteValidator` — checks entity-level ACL (`integration:create` is sufficient)\n2. `EntityProtectionValidator` — checks `WriteProtection` on entity definitions, but `IntegrationDefinition` has none\n\nThe `admin` field in `IntegrationDefinition` is a plain `BoolField` with no `WriteProtection` or special flag. The Sync API writes it without restriction.\n\n**Vulnerable code path:**\n- `src/Core/Framewo","public_affected_ranges":["< 6.6.10.18"]},{"certainty":"source_listed","source_ids":["sr-6278f281f4dd8a709451e0d284c8a839"],"technology":"shopware/platform","known_exclusions":[],"conditions_summary":"## Summary\n\nA non-admin API user with `integration:create` ACL privilege can escalate to full administrator by creating an integration with `admin: true` through the Sync API (`POST /api/_action/sync`). The regular integration endpoint (`POST /api/integration`) correctly blocks this, but the Sync API bypasses the controller-level check by writing directly through the DAL EntityWriter. The `integration` entity definition lacks `WriteProtection`, and the `admin` field has no field-level restriction flag.\n\n**OWASP:** A01:2021 — Broken Access Control\n\n## Root Cause\n\n`IntegrationController::upsertIntegration()` checks `$source->isAdmin()` before allowing the `admin` field to be set. However, `SyncController::sync()` routes writes through `SyncService → EntityWriter`, which only applies:\n\n1. `AclWriteValidator` — checks entity-level ACL (`integration:create` is sufficient)\n2. `EntityProtectionValidator` — checks `WriteProtection` on entity definitions, but `IntegrationDefinition` has none\n\nThe `admin` field in `IntegrationDefinition` is a plain `BoolField` with no `WriteProtection` or special flag. The Sync API writes it without restriction.\n\n**Vulnerable code path:**\n- `src/Core/Framewo","public_affected_ranges":["ECOSYSTEM: introduced 6.7.0.0; fixed 6.7.10.1"]},{"certainty":"source_listed","source_ids":["sr-6278f281f4dd8a709451e0d284c8a839"],"technology":"shopware/platform","known_exclusions":[],"conditions_summary":"## Summary\n\nA non-admin API user with `integration:create` ACL privilege can escalate to full administrator by creating an integration with `admin: true` through the Sync API (`POST /api/_action/sync`). The regular integration endpoint (`POST /api/integration`) correctly blocks this, but the Sync API bypasses the controller-level check by writing directly through the DAL EntityWriter. The `integration` entity definition lacks `WriteProtection`, and the `admin` field has no field-level restriction flag.\n\n**OWASP:** A01:2021 — Broken Access Control\n\n## Root Cause\n\n`IntegrationController::upsertIntegration()` checks `$source->isAdmin()` before allowing the `admin` field to be set. However, `SyncController::sync()` routes writes through `SyncService → EntityWriter`, which only applies:\n\n1. `AclWriteValidator` — checks entity-level ACL (`integration:create` is sufficient)\n2. `EntityProtectionValidator` — checks `WriteProtection` on entity definitions, but `IntegrationDefinition` has none\n\nThe `admin` field in `IntegrationDefinition` is a plain `BoolField` with no `WriteProtection` or special flag. The Sync API writes it without restriction.\n\n**Vulnerable code path:**\n- `src/Core/Framewo","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.6.10.18"]},{"certainty":"source_listed","source_ids":["sr-6278f281f4dd8a709451e0d284c8a839"],"technology":"shopware/core","known_exclusions":[],"conditions_summary":"## Summary\n\nA non-admin API user with `integration:create` ACL privilege can escalate to full administrator by creating an integration with `admin: true` through the Sync API (`POST /api/_action/sync`). The regular integration endpoint (`POST /api/integration`) correctly blocks this, but the Sync API bypasses the controller-level check by writing directly through the DAL EntityWriter. The `integration` entity definition lacks `WriteProtection`, and the `admin` field has no field-level restriction flag.\n\n**OWASP:** A01:2021 — Broken Access Control\n\n## Root Cause\n\n`IntegrationController::upsertIntegration()` checks `$source->isAdmin()` before allowing the `admin` field to be set. However, `SyncController::sync()` routes writes through `SyncService → EntityWriter`, which only applies:\n\n1. `AclWriteValidator` — checks entity-level ACL (`integration:create` is sufficient)\n2. `EntityProtectionValidator` — checks `WriteProtection` on entity definitions, but `IntegrationDefinition` has none\n\nThe `admin` field in `IntegrationDefinition` is a plain `BoolField` with no `WriteProtection` or special flag. The Sync API writes it without restriction.\n\n**Vulnerable code path:**\n- `src/Core/Framewo","public_affected_ranges":["ECOSYSTEM: introduced 6.7.0.0; fixed 6.7.10.1"]},{"certainty":"source_listed","source_ids":["sr-6278f281f4dd8a709451e0d284c8a839"],"technology":"shopware/core","known_exclusions":[],"conditions_summary":"## Summary\n\nA non-admin API user with `integration:create` ACL privilege can escalate to full administrator by creating an integration with `admin: true` through the Sync API (`POST /api/_action/sync`). The regular integration endpoint (`POST /api/integration`) correctly blocks this, but the Sync API bypasses the controller-level check by writing directly through the DAL EntityWriter. The `integration` entity definition lacks `WriteProtection`, and the `admin` field has no field-level restriction flag.\n\n**OWASP:** A01:2021 — Broken Access Control\n\n## Root Cause\n\n`IntegrationController::upsertIntegration()` checks `$source->isAdmin()` before allowing the `admin` field to be set. However, `SyncController::sync()` routes writes through `SyncService → EntityWriter`, which only applies:\n\n1. `AclWriteValidator` — checks entity-level ACL (`integration:create` is sufficient)\n2. `EntityProtectionValidator` — checks `WriteProtection` on entity definitions, but `IntegrationDefinition` has none\n\nThe `admin` field in `IntegrationDefinition` is a plain `BoolField` with no `WriteProtection` or special flag. The Sync API writes it without restriction.\n\n**Vulnerable code path:**\n- `src/Core/Framewo","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.6.10.18"]}],"null_published_at":"2026-11-07T07:07:39.813Z","source_updated_at":"2026-06-04T19:23:34.000Z","source_disclosed_at":"2026-06-04T19:23:33.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.422Z"},{"id":"NVI-00004333","kind":"vulnerability","title":"Shopware: Privilege Escalation via Sync API Integration Admin Flag Bypass","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-gv8p-48fr-4fxg","CVE-2026-48008"],"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-6278f281f4dd8a709451e0d284c8a839"],"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-6278f281f4dd8a709451e0d284c8a839"],"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-6278f281f4dd8a709451e0d284c8a839"],"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-6278f281f4dd8a709451e0d284c8a839"],"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-3d1365f21aea5bf68e7b9c8c57d5e90a"],"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.472%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.40833. Missing scores are unknown.","source_id":"sr-3d1365f21aea5bf68e7b9c8c57d5e90a"}],"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-6278f281f4dd8a709451e0d284c8a839","url":"https://github.com/advisories/GHSA-gv8p-48fr-4fxg","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-gv8p-48fr-4fxg","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:20.422Z"},{"id":"sr-3d1365f21aea5bf68e7b9c8c57d5e90a","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-48008","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.379Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-6278f281f4dd8a709451e0d284c8a839"],"technology":"shopware/platform","known_exclusions":[],"conditions_summary":"## Summary\n\nA non-admin API user with `integration:create` ACL privilege can escalate to full administrator by creating an integration with `admin: true` through the Sync API (`POST /api/_action/sync`). The regular integration endpoint (`POST /api/integration`) correctly blocks this, but the Sync API bypasses the controller-level check by writing directly through the DAL EntityWriter. The `integration` entity definition lacks `WriteProtection`, and the `admin` field has no field-level restriction flag.\n\n**OWASP:** A01:2021 — Broken Access Control\n\n## Root Cause\n\n`IntegrationController::upsertIntegration()` checks `$source->isAdmin()` before allowing the `admin` field to be set. However, `SyncController::sync()` routes writes through `SyncService → EntityWriter`, which only applies:\n\n1. `AclWriteValidator` — checks entity-level ACL (`integration:create` is sufficient)\n2. `EntityProtectionValidator` — checks `WriteProtection` on entity definitions, but `IntegrationDefinition` has none\n\nThe `admin` field in `IntegrationDefinition` is a plain `BoolField` with no `WriteProtection` or special flag. The Sync API writes it without restriction.\n\n**Vulnerable code path:**\n- `src/Core/Framewo","public_affected_ranges":["ECOSYSTEM: introduced 6.7.0.0; fixed 6.7.10.1"]},{"certainty":"source_listed","source_ids":["sr-6278f281f4dd8a709451e0d284c8a839"],"technology":"shopware/platform","known_exclusions":[],"conditions_summary":"## Summary\n\nA non-admin API user with `integration:create` ACL privilege can escalate to full administrator by creating an integration with `admin: true` through the Sync API (`POST /api/_action/sync`). The regular integration endpoint (`POST /api/integration`) correctly blocks this, but the Sync API bypasses the controller-level check by writing directly through the DAL EntityWriter. The `integration` entity definition lacks `WriteProtection`, and the `admin` field has no field-level restriction flag.\n\n**OWASP:** A01:2021 — Broken Access Control\n\n## Root Cause\n\n`IntegrationController::upsertIntegration()` checks `$source->isAdmin()` before allowing the `admin` field to be set. However, `SyncController::sync()` routes writes through `SyncService → EntityWriter`, which only applies:\n\n1. `AclWriteValidator` — checks entity-level ACL (`integration:create` is sufficient)\n2. `EntityProtectionValidator` — checks `WriteProtection` on entity definitions, but `IntegrationDefinition` has none\n\nThe `admin` field in `IntegrationDefinition` is a plain `BoolField` with no `WriteProtection` or special flag. The Sync API writes it without restriction.\n\n**Vulnerable code path:**\n- `src/Core/Framewo","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.6.10.18"]},{"certainty":"source_listed","source_ids":["sr-6278f281f4dd8a709451e0d284c8a839"],"technology":"shopware/core","known_exclusions":[],"conditions_summary":"## Summary\n\nA non-admin API user with `integration:create` ACL privilege can escalate to full administrator by creating an integration with `admin: true` through the Sync API (`POST /api/_action/sync`). The regular integration endpoint (`POST /api/integration`) correctly blocks this, but the Sync API bypasses the controller-level check by writing directly through the DAL EntityWriter. The `integration` entity definition lacks `WriteProtection`, and the `admin` field has no field-level restriction flag.\n\n**OWASP:** A01:2021 — Broken Access Control\n\n## Root Cause\n\n`IntegrationController::upsertIntegration()` checks `$source->isAdmin()` before allowing the `admin` field to be set. However, `SyncController::sync()` routes writes through `SyncService → EntityWriter`, which only applies:\n\n1. `AclWriteValidator` — checks entity-level ACL (`integration:create` is sufficient)\n2. `EntityProtectionValidator` — checks `WriteProtection` on entity definitions, but `IntegrationDefinition` has none\n\nThe `admin` field in `IntegrationDefinition` is a plain `BoolField` with no `WriteProtection` or special flag. The Sync API writes it without restriction.\n\n**Vulnerable code path:**\n- `src/Core/Framewo","public_affected_ranges":["ECOSYSTEM: introduced 6.7.0.0; fixed 6.7.10.1"]},{"certainty":"source_listed","source_ids":["sr-6278f281f4dd8a709451e0d284c8a839"],"technology":"shopware/core","known_exclusions":[],"conditions_summary":"## Summary\n\nA non-admin API user with `integration:create` ACL privilege can escalate to full administrator by creating an integration with `admin: true` through the Sync API (`POST /api/_action/sync`). The regular integration endpoint (`POST /api/integration`) correctly blocks this, but the Sync API bypasses the controller-level check by writing directly through the DAL EntityWriter. The `integration` entity definition lacks `WriteProtection`, and the `admin` field has no field-level restriction flag.\n\n**OWASP:** A01:2021 — Broken Access Control\n\n## Root Cause\n\n`IntegrationController::upsertIntegration()` checks `$source->isAdmin()` before allowing the `admin` field to be set. However, `SyncController::sync()` routes writes through `SyncService → EntityWriter`, which only applies:\n\n1. `AclWriteValidator` — checks entity-level ACL (`integration:create` is sufficient)\n2. `EntityProtectionValidator` — checks `WriteProtection` on entity definitions, but `IntegrationDefinition` has none\n\nThe `admin` field in `IntegrationDefinition` is a plain `BoolField` with no `WriteProtection` or special flag. The Sync API writes it without restriction.\n\n**Vulnerable code path:**\n- `src/Core/Framewo","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.6.10.18"]}],"null_published_at":"2026-10-31T22:27:15.299Z","source_updated_at":"2026-09-10T03:51:08.823Z","source_disclosed_at":"2026-06-04T19:23:33.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:20.422Z"},{"id":"NVI-00004333","kind":"vulnerability","title":"Shopware: Privilege Escalation via Sync API Integration Admin Flag Bypass","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-gv8p-48fr-4fxg","CVE-2026-48008"],"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-6278f281f4dd8a709451e0d284c8a839"],"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-6278f281f4dd8a709451e0d284c8a839"],"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-6278f281f4dd8a709451e0d284c8a839"],"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-6278f281f4dd8a709451e0d284c8a839"],"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-6278f281f4dd8a709451e0d284c8a839","url":"https://github.com/advisories/GHSA-gv8p-48fr-4fxg","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-gv8p-48fr-4fxg","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:20.422Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-6278f281f4dd8a709451e0d284c8a839"],"technology":"shopware/platform","known_exclusions":[],"conditions_summary":"## Summary\n\nA non-admin API user with `integration:create` ACL privilege can escalate to full administrator by creating an integration with `admin: true` through the Sync API (`POST /api/_action/sync`). The regular integration endpoint (`POST /api/integration`) correctly blocks this, but the Sync API bypasses the controller-level check by writing directly through the DAL EntityWriter. The `integration` entity definition lacks `WriteProtection`, and the `admin` field has no field-level restriction flag.\n\n**OWASP:** A01:2021 — Broken Access Control\n\n## Root Cause\n\n`IntegrationController::upsertIntegration()` checks `$source->isAdmin()` before allowing the `admin` field to be set. However, `SyncController::sync()` routes writes through `SyncService → EntityWriter`, which only applies:\n\n1. `AclWriteValidator` — checks entity-level ACL (`integration:create` is sufficient)\n2. `EntityProtectionValidator` — checks `WriteProtection` on entity definitions, but `IntegrationDefinition` has none\n\nThe `admin` field in `IntegrationDefinition` is a plain `BoolField` with no `WriteProtection` or special flag. The Sync API writes it without restriction.\n\n**Vulnerable code path:**\n- `src/Core/Framewo","public_affected_ranges":["ECOSYSTEM: introduced 6.7.0.0; fixed 6.7.10.1"]},{"certainty":"source_listed","source_ids":["sr-6278f281f4dd8a709451e0d284c8a839"],"technology":"shopware/platform","known_exclusions":[],"conditions_summary":"## Summary\n\nA non-admin API user with `integration:create` ACL privilege can escalate to full administrator by creating an integration with `admin: true` through the Sync API (`POST /api/_action/sync`). The regular integration endpoint (`POST /api/integration`) correctly blocks this, but the Sync API bypasses the controller-level check by writing directly through the DAL EntityWriter. The `integration` entity definition lacks `WriteProtection`, and the `admin` field has no field-level restriction flag.\n\n**OWASP:** A01:2021 — Broken Access Control\n\n## Root Cause\n\n`IntegrationController::upsertIntegration()` checks `$source->isAdmin()` before allowing the `admin` field to be set. However, `SyncController::sync()` routes writes through `SyncService → EntityWriter`, which only applies:\n\n1. `AclWriteValidator` — checks entity-level ACL (`integration:create` is sufficient)\n2. `EntityProtectionValidator` — checks `WriteProtection` on entity definitions, but `IntegrationDefinition` has none\n\nThe `admin` field in `IntegrationDefinition` is a plain `BoolField` with no `WriteProtection` or special flag. The Sync API writes it without restriction.\n\n**Vulnerable code path:**\n- `src/Core/Framewo","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.6.10.18"]},{"certainty":"source_listed","source_ids":["sr-6278f281f4dd8a709451e0d284c8a839"],"technology":"shopware/core","known_exclusions":[],"conditions_summary":"## Summary\n\nA non-admin API user with `integration:create` ACL privilege can escalate to full administrator by creating an integration with `admin: true` through the Sync API (`POST /api/_action/sync`). The regular integration endpoint (`POST /api/integration`) correctly blocks this, but the Sync API bypasses the controller-level check by writing directly through the DAL EntityWriter. The `integration` entity definition lacks `WriteProtection`, and the `admin` field has no field-level restriction flag.\n\n**OWASP:** A01:2021 — Broken Access Control\n\n## Root Cause\n\n`IntegrationController::upsertIntegration()` checks `$source->isAdmin()` before allowing the `admin` field to be set. However, `SyncController::sync()` routes writes through `SyncService → EntityWriter`, which only applies:\n\n1. `AclWriteValidator` — checks entity-level ACL (`integration:create` is sufficient)\n2. `EntityProtectionValidator` — checks `WriteProtection` on entity definitions, but `IntegrationDefinition` has none\n\nThe `admin` field in `IntegrationDefinition` is a plain `BoolField` with no `WriteProtection` or special flag. The Sync API writes it without restriction.\n\n**Vulnerable code path:**\n- `src/Core/Framewo","public_affected_ranges":["ECOSYSTEM: introduced 6.7.0.0; fixed 6.7.10.1"]},{"certainty":"source_listed","source_ids":["sr-6278f281f4dd8a709451e0d284c8a839"],"technology":"shopware/core","known_exclusions":[],"conditions_summary":"## Summary\n\nA non-admin API user with `integration:create` ACL privilege can escalate to full administrator by creating an integration with `admin: true` through the Sync API (`POST /api/_action/sync`). The regular integration endpoint (`POST /api/integration`) correctly blocks this, but the Sync API bypasses the controller-level check by writing directly through the DAL EntityWriter. The `integration` entity definition lacks `WriteProtection`, and the `admin` field has no field-level restriction flag.\n\n**OWASP:** A01:2021 — Broken Access Control\n\n## Root Cause\n\n`IntegrationController::upsertIntegration()` checks `$source->isAdmin()` before allowing the `admin` field to be set. However, `SyncController::sync()` routes writes through `SyncService → EntityWriter`, which only applies:\n\n1. `AclWriteValidator` — checks entity-level ACL (`integration:create` is sufficient)\n2. `EntityProtectionValidator` — checks `WriteProtection` on entity definitions, but `IntegrationDefinition` has none\n\nThe `admin` field in `IntegrationDefinition` is a plain `BoolField` with no `WriteProtection` or special flag. The Sync API writes it without restriction.\n\n**Vulnerable code path:**\n- `src/Core/Framewo","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.6.10.18"]}],"null_published_at":"2026-10-31T22:12:52.643Z","source_updated_at":"2026-09-10T03:51:08.823Z","source_disclosed_at":"2026-06-04T19:23:33.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.422Z"}],"next_cursor":null,"snapshot_revision":"42594"}