{"items":[{"id":"NVI-00004424","kind":"vulnerability","title":"October CMS: Editor Sub-Permission Bypass for Asset and Blueprint File Operations","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-jvwg-phxx-j3rp","CVE-2026-29179"],"plain_summary":"OSV carries this publisher advisory for october/system, october/system. 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 4.1.16 for october/system. Confirm the publisher’s latest guidance.","source_ids":["sr-65a41183fc6e5b133959b964b5f80924"],"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 3.7.16 for october/system. Confirm the publisher’s latest guidance.","source_ids":["sr-65a41183fc6e5b133959b964b5f80924"],"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-2fd7684fbcb5c53499b76b4c97dc094c"],"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-10-26T21:10:00.170Z","value":"3.3 LOW (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-c0600229d0e4d46ffd1e8e97efa934d7"},{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.144%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.03646. Missing scores are unknown.","source_id":"sr-2fd7684fbcb5c53499b76b4c97dc094c"}],"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-65a41183fc6e5b133959b964b5f80924","url":"https://github.com/advisories/GHSA-jvwg-phxx-j3rp","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-jvwg-phxx-j3rp","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.970Z"},{"id":"sr-c0600229d0e4d46ffd1e8e97efa934d7","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-29179","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-29179","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T01:40:56.268Z"},{"id":"sr-2fd7684fbcb5c53499b76b4c97dc094c","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-29179","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.376Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-65a41183fc6e5b133959b964b5f80924"],"technology":"october/system","known_exclusions":[],"conditions_summary":"Fine-grained sub-permission checks for asset and blueprint file operations were not enforced in the CMS and Tailor editor extensions. This only affects backend users who were explicitly granted `editor` access but had `editor.cms_assets` or `editor.tailor_blueprints` specifically withheld, an uncommon permission configuration. In this edge case, such users could perform file operations (create, delete, rename, move, upload) on theme assets or blueprint files despite lacking the required sub-permission. A related operator precedence error in the Tailor navigation also disclosed the theme blueprint directory tree under the same conditions.\n\n### Impact\n- Only exploitable by authenticated backend users with `editor` access who have been specifically denied the `editor.cms_assets` or `editor.tailor_blueprints` sub-permissions\n- Does not affect default permission configurations where editor users typically have all sub-permissions granted\n- Users without `editor.cms_assets` could manipulate theme asset files (delete, rename, move, upload, create directories)\n- Users without `editor.tailor_blueprints` could manipulate blueprint files (delete, rename, move, upload, create directories)\n- Us","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0; fixed 4.1.16"]},{"certainty":"source_listed","source_ids":["sr-65a41183fc6e5b133959b964b5f80924"],"technology":"october/system","known_exclusions":[],"conditions_summary":"Fine-grained sub-permission checks for asset and blueprint file operations were not enforced in the CMS and Tailor editor extensions. This only affects backend users who were explicitly granted `editor` access but had `editor.cms_assets` or `editor.tailor_blueprints` specifically withheld, an uncommon permission configuration. In this edge case, such users could perform file operations (create, delete, rename, move, upload) on theme assets or blueprint files despite lacking the required sub-permission. A related operator precedence error in the Tailor navigation also disclosed the theme blueprint directory tree under the same conditions.\n\n### Impact\n- Only exploitable by authenticated backend users with `editor` access who have been specifically denied the `editor.cms_assets` or `editor.tailor_blueprints` sub-permissions\n- Does not affect default permission configurations where editor users typically have all sub-permissions granted\n- Users without `editor.cms_assets` could manipulate theme asset files (delete, rename, move, upload, create directories)\n- Users without `editor.tailor_blueprints` could manipulate blueprint files (delete, rename, move, upload, create directories)\n- Us","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 3.7.16"]}],"null_published_at":"2026-11-07T22:29:23.382Z","source_updated_at":"2026-05-05T16:08:46.538Z","source_disclosed_at":"2026-04-21T17:15:38.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:30.970Z"},{"id":"NVI-00004424","kind":"vulnerability","title":"October CMS: Editor Sub-Permission Bypass for Asset and Blueprint File Operations","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-jvwg-phxx-j3rp","CVE-2026-29179"],"plain_summary":"OSV carries this publisher advisory for october/system, october/system. 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 4.1.16 for october/system. Confirm the publisher’s latest guidance.","source_ids":["sr-65a41183fc6e5b133959b964b5f80924"],"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 3.7.16 for october/system. Confirm the publisher’s latest guidance.","source_ids":["sr-65a41183fc6e5b133959b964b5f80924"],"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-2fd7684fbcb5c53499b76b4c97dc094c"],"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.144%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.03646. Missing scores are unknown.","source_id":"sr-2fd7684fbcb5c53499b76b4c97dc094c"}],"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-65a41183fc6e5b133959b964b5f80924","url":"https://github.com/advisories/GHSA-jvwg-phxx-j3rp","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-jvwg-phxx-j3rp","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.970Z"},{"id":"sr-2fd7684fbcb5c53499b76b4c97dc094c","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-29179","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:15.376Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-65a41183fc6e5b133959b964b5f80924"],"technology":"october/system","known_exclusions":[],"conditions_summary":"Fine-grained sub-permission checks for asset and blueprint file operations were not enforced in the CMS and Tailor editor extensions. This only affects backend users who were explicitly granted `editor` access but had `editor.cms_assets` or `editor.tailor_blueprints` specifically withheld, an uncommon permission configuration. In this edge case, such users could perform file operations (create, delete, rename, move, upload) on theme assets or blueprint files despite lacking the required sub-permission. A related operator precedence error in the Tailor navigation also disclosed the theme blueprint directory tree under the same conditions.\n\n### Impact\n- Only exploitable by authenticated backend users with `editor` access who have been specifically denied the `editor.cms_assets` or `editor.tailor_blueprints` sub-permissions\n- Does not affect default permission configurations where editor users typically have all sub-permissions granted\n- Users without `editor.cms_assets` could manipulate theme asset files (delete, rename, move, upload, create directories)\n- Users without `editor.tailor_blueprints` could manipulate blueprint files (delete, rename, move, upload, create directories)\n- Us","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0; fixed 4.1.16"]},{"certainty":"source_listed","source_ids":["sr-65a41183fc6e5b133959b964b5f80924"],"technology":"october/system","known_exclusions":[],"conditions_summary":"Fine-grained sub-permission checks for asset and blueprint file operations were not enforced in the CMS and Tailor editor extensions. This only affects backend users who were explicitly granted `editor` access but had `editor.cms_assets` or `editor.tailor_blueprints` specifically withheld, an uncommon permission configuration. In this edge case, such users could perform file operations (create, delete, rename, move, upload) on theme assets or blueprint files despite lacking the required sub-permission. A related operator precedence error in the Tailor navigation also disclosed the theme blueprint directory tree under the same conditions.\n\n### Impact\n- Only exploitable by authenticated backend users with `editor` access who have been specifically denied the `editor.cms_assets` or `editor.tailor_blueprints` sub-permissions\n- Does not affect default permission configurations where editor users typically have all sub-permissions granted\n- Users without `editor.cms_assets` could manipulate theme asset files (delete, rename, move, upload, create directories)\n- Users without `editor.tailor_blueprints` could manipulate blueprint files (delete, rename, move, upload, create directories)\n- Us","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 3.7.16"]}],"null_published_at":"2026-10-31T22:27:15.282Z","source_updated_at":"2026-05-05T16:08:46.538Z","source_disclosed_at":"2026-04-21T17:15:38.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:30.970Z"},{"id":"NVI-00004424","kind":"vulnerability","title":"October CMS: Editor Sub-Permission Bypass for Asset and Blueprint File Operations","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-jvwg-phxx-j3rp","CVE-2026-29179"],"plain_summary":"OSV carries this publisher advisory for october/system, october/system. 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 4.1.16 for october/system. Confirm the publisher’s latest guidance.","source_ids":["sr-65a41183fc6e5b133959b964b5f80924"],"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 3.7.16 for october/system. Confirm the publisher’s latest guidance.","source_ids":["sr-65a41183fc6e5b133959b964b5f80924"],"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-65a41183fc6e5b133959b964b5f80924","url":"https://github.com/advisories/GHSA-jvwg-phxx-j3rp","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-jvwg-phxx-j3rp","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:42:30.970Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-65a41183fc6e5b133959b964b5f80924"],"technology":"october/system","known_exclusions":[],"conditions_summary":"Fine-grained sub-permission checks for asset and blueprint file operations were not enforced in the CMS and Tailor editor extensions. This only affects backend users who were explicitly granted `editor` access but had `editor.cms_assets` or `editor.tailor_blueprints` specifically withheld, an uncommon permission configuration. In this edge case, such users could perform file operations (create, delete, rename, move, upload) on theme assets or blueprint files despite lacking the required sub-permission. A related operator precedence error in the Tailor navigation also disclosed the theme blueprint directory tree under the same conditions.\n\n### Impact\n- Only exploitable by authenticated backend users with `editor` access who have been specifically denied the `editor.cms_assets` or `editor.tailor_blueprints` sub-permissions\n- Does not affect default permission configurations where editor users typically have all sub-permissions granted\n- Users without `editor.cms_assets` could manipulate theme asset files (delete, rename, move, upload, create directories)\n- Users without `editor.tailor_blueprints` could manipulate blueprint files (delete, rename, move, upload, create directories)\n- Us","public_affected_ranges":["ECOSYSTEM: introduced 4.0.0; fixed 4.1.16"]},{"certainty":"source_listed","source_ids":["sr-65a41183fc6e5b133959b964b5f80924"],"technology":"october/system","known_exclusions":[],"conditions_summary":"Fine-grained sub-permission checks for asset and blueprint file operations were not enforced in the CMS and Tailor editor extensions. This only affects backend users who were explicitly granted `editor` access but had `editor.cms_assets` or `editor.tailor_blueprints` specifically withheld, an uncommon permission configuration. In this edge case, such users could perform file operations (create, delete, rename, move, upload) on theme assets or blueprint files despite lacking the required sub-permission. A related operator precedence error in the Tailor navigation also disclosed the theme blueprint directory tree under the same conditions.\n\n### Impact\n- Only exploitable by authenticated backend users with `editor` access who have been specifically denied the `editor.cms_assets` or `editor.tailor_blueprints` sub-permissions\n- Does not affect default permission configurations where editor users typically have all sub-permissions granted\n- Users without `editor.cms_assets` could manipulate theme asset files (delete, rename, move, upload, create directories)\n- Users without `editor.tailor_blueprints` could manipulate blueprint files (delete, rename, move, upload, create directories)\n- Us","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 3.7.16"]}],"null_published_at":"2026-10-31T22:12:57.124Z","source_updated_at":"2026-05-05T16:08:46.538Z","source_disclosed_at":"2026-04-21T17:15:38.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:30.970Z"}],"next_cursor":null,"snapshot_revision":"42594"}