{"items":[{"id":"NVI-00016279","kind":"vulnerability","title":"n8n: External Secrets Permission Bypass via Expression Parser Mismatch","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-jp7m-xcgx-57qm","CVE-2026-59259"],"plain_summary":"GitHub lists this reviewed advisory for n8n, n8n, n8n. 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-5d595dcb1ea318f5923a4524cb44d11e"],"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":[],"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-5d595dcb1ea318f5923a4524cb44d11e","url":"https://github.com/advisories/GHSA-jp7m-xcgx-57qm","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-jp7m-xcgx-57qm","publisher":"GitHub Advisory Database","observed_at":"2026-11-03T17:42:43.803Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-5d595dcb1ea318f5923a4524cb44d11e"],"technology":"n8n","known_exclusions":[],"conditions_summary":"## Impact\nDue to a mismatch between the static validation check and the runtime expression engine, an authenticated user with credential create or update permissions, but without the `externalSecret:list` scope, could embed external secret references into credentials in forms the validation did not detect. These references would resolve at workflow execution time, exposing secret values the user was not authorized to access.\n\nThis issue only affects instances where an external secrets provider is configured and Advanced Permissions are in use.\n\n## Patches\nThe issue has been fixed in n8n versions 1.123.61, 2.27.4, and 2.28.1. Users should upgrade to one of these versions or later to remediate the vulnerability.\n\n## Workarounds\nIf upgrading is not immediately possible, administrators should consider the following temporary mitigations:\n- Restrict credential creation and update permissions to fully trusted users only.\n- Audit existing credentials for unexpected external secret references.\n\nThese workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.","public_affected_ranges":["< 1.123.61"]},{"certainty":"source_listed","source_ids":["sr-5d595dcb1ea318f5923a4524cb44d11e"],"technology":"n8n","known_exclusions":[],"conditions_summary":"## Impact\nDue to a mismatch between the static validation check and the runtime expression engine, an authenticated user with credential create or update permissions, but without the `externalSecret:list` scope, could embed external secret references into credentials in forms the validation did not detect. These references would resolve at workflow execution time, exposing secret values the user was not authorized to access.\n\nThis issue only affects instances where an external secrets provider is configured and Advanced Permissions are in use.\n\n## Patches\nThe issue has been fixed in n8n versions 1.123.61, 2.27.4, and 2.28.1. Users should upgrade to one of these versions or later to remediate the vulnerability.\n\n## Workarounds\nIf upgrading is not immediately possible, administrators should consider the following temporary mitigations:\n- Restrict credential creation and update permissions to fully trusted users only.\n- Audit existing credentials for unexpected external secret references.\n\nThese workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.","public_affected_ranges":[">= 2.28.0, < 2.28.1"]},{"certainty":"source_listed","source_ids":["sr-5d595dcb1ea318f5923a4524cb44d11e"],"technology":"n8n","known_exclusions":[],"conditions_summary":"## Impact\nDue to a mismatch between the static validation check and the runtime expression engine, an authenticated user with credential create or update permissions, but without the `externalSecret:list` scope, could embed external secret references into credentials in forms the validation did not detect. These references would resolve at workflow execution time, exposing secret values the user was not authorized to access.\n\nThis issue only affects instances where an external secrets provider is configured and Advanced Permissions are in use.\n\n## Patches\nThe issue has been fixed in n8n versions 1.123.61, 2.27.4, and 2.28.1. Users should upgrade to one of these versions or later to remediate the vulnerability.\n\n## Workarounds\nIf upgrading is not immediately possible, administrators should consider the following temporary mitigations:\n- Restrict credential creation and update permissions to fully trusted users only.\n- Audit existing credentials for unexpected external secret references.\n\nThese workarounds do not fully remediate the risk and should only be used as short-term mitigation measures.","public_affected_ranges":[">= 2.0.0-rc.0, < 2.27.4"]}],"null_published_at":"2026-11-04T10:04:27.926Z","source_updated_at":"2026-07-22T22:21:21.000Z","source_disclosed_at":"2026-07-22T22:21:20.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-11-03T17:42:43.803Z"}],"next_cursor":null,"snapshot_revision":"42594"}