{"items":[{"id":"NVI-00016058","kind":"vulnerability","title":"n8n Has a Source Control Pull SQL Injection","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-mhrx-qhrj-673w","CVE-2026-44792"],"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-15a919639d09a5cca8ce3760490ef2d0"],"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-20T13:41:03.000Z","value":"9 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-11f9d25e339a1431b99c0c087c5cb86a"},{"kind":"CVSS","as_of":"2026-10-26T11:10:00.157Z","value":"9 CRITICAL (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-5a2d413b59ecdc29928c753d891e3910"},{"kind":"CVSS","as_of":"2026-10-26T11:10:00.157Z","value":"8.9 HIGH (4.0)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-5a2d413b59ecdc29928c753d891e3910"},{"kind":"EPSS","as_of":"2026-11-04T12:03:12.000Z","value":"0.387%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.32943. Missing scores are unknown.","source_id":"sr-15a919639d09a5cca8ce3760490ef2d0"}],"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-11f9d25e339a1431b99c0c087c5cb86a","url":"https://github.com/advisories/GHSA-mhrx-qhrj-673w","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-mhrx-qhrj-673w","publisher":"GitHub Advisory Database","observed_at":"2026-11-04T02:49:06.528Z"},{"id":"sr-5a2d413b59ecdc29928c753d891e3910","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-44792","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2026-44792","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-08T01:47:29.046Z"},{"id":"sr-15a919639d09a5cca8ce3760490ef2d0","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-44792","publisher":"FIRST EPSS","observed_at":"2026-11-04T17:58:50.327Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-11f9d25e339a1431b99c0c087c5cb86a"],"technology":"n8n","known_exclusions":[],"conditions_summary":"## Impact\nAn attacker with write access to the git repository connected to an n8n Source Control configuration could commit a malicious Data Table JSON file containing a crafted column name. When an administrator performed a Source Control Pull, n8n imported the file and could lead to SQL injection on the internal PostgreSQL instance.\n\nExploitation requires all of the following conditions:\n- The n8n instance uses PostgreSQL as its database backend.\n- The Source Control feature is enabled and connected to a repository the attacker can write to.\n- An administrator triggers a Source Control Pull.\n\n## Patches\nThe issue has been fixed in n8n version 1.123.43, 2.20.7, and 2.21.1. Users should upgrade to this version or later to remediate the vulnerability.\n\n## Workarounds\nIf upgrading is not immediately possible, administrators should consider the following temporary mitigations:\n- Disable the Source Control feature if it is not actively required.\n- Restrict write access to the connected git repository to fully trusted users only.\n- Avoid pulling from repositories that may have been modified by untrusted parties.\n\nThese workarounds do not fully remediate the risk and should only be used ","public_affected_ranges":["< 1.123.43"]},{"certainty":"source_listed","source_ids":["sr-11f9d25e339a1431b99c0c087c5cb86a"],"technology":"n8n","known_exclusions":[],"conditions_summary":"## Impact\nAn attacker with write access to the git repository connected to an n8n Source Control configuration could commit a malicious Data Table JSON file containing a crafted column name. When an administrator performed a Source Control Pull, n8n imported the file and could lead to SQL injection on the internal PostgreSQL instance.\n\nExploitation requires all of the following conditions:\n- The n8n instance uses PostgreSQL as its database backend.\n- The Source Control feature is enabled and connected to a repository the attacker can write to.\n- An administrator triggers a Source Control Pull.\n\n## Patches\nThe issue has been fixed in n8n version 1.123.43, 2.20.7, and 2.21.1. Users should upgrade to this version or later to remediate the vulnerability.\n\n## Workarounds\nIf upgrading is not immediately possible, administrators should consider the following temporary mitigations:\n- Disable the Source Control feature if it is not actively required.\n- Restrict write access to the connected git repository to fully trusted users only.\n- Avoid pulling from repositories that may have been modified by untrusted parties.\n\nThese workarounds do not fully remediate the risk and should only be used ","public_affected_ranges":[">= 2.21.0, < 2.21.1"]},{"certainty":"source_listed","source_ids":["sr-11f9d25e339a1431b99c0c087c5cb86a"],"technology":"n8n","known_exclusions":[],"conditions_summary":"## Impact\nAn attacker with write access to the git repository connected to an n8n Source Control configuration could commit a malicious Data Table JSON file containing a crafted column name. When an administrator performed a Source Control Pull, n8n imported the file and could lead to SQL injection on the internal PostgreSQL instance.\n\nExploitation requires all of the following conditions:\n- The n8n instance uses PostgreSQL as its database backend.\n- The Source Control feature is enabled and connected to a repository the attacker can write to.\n- An administrator triggers a Source Control Pull.\n\n## Patches\nThe issue has been fixed in n8n version 1.123.43, 2.20.7, and 2.21.1. Users should upgrade to this version or later to remediate the vulnerability.\n\n## Workarounds\nIf upgrading is not immediately possible, administrators should consider the following temporary mitigations:\n- Disable the Source Control feature if it is not actively required.\n- Restrict write access to the connected git repository to fully trusted users only.\n- Avoid pulling from repositories that may have been modified by untrusted parties.\n\nThese workarounds do not fully remediate the risk and should only be used ","public_affected_ranges":[">= 2.0.0-rc.0, < 2.20.7"]}],"null_published_at":"2026-11-08T19:53:44.059Z","source_updated_at":"2026-07-20T13:41:03.000Z","source_disclosed_at":"2026-05-14T16:18:00.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-11-04T02:49:06.528Z"},{"id":"NVI-00016058","kind":"vulnerability","title":"n8n Has a Source Control Pull SQL Injection","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-mhrx-qhrj-673w","CVE-2026-44792"],"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-11f9d25e339a1431b99c0c087c5cb86a"],"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-20T13:41:03.000Z","value":"9 high","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-11f9d25e339a1431b99c0c087c5cb86a"}],"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-11f9d25e339a1431b99c0c087c5cb86a","url":"https://github.com/advisories/GHSA-mhrx-qhrj-673w","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-mhrx-qhrj-673w","publisher":"GitHub Advisory Database","observed_at":"2026-11-04T02:49:06.528Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-11f9d25e339a1431b99c0c087c5cb86a"],"technology":"n8n","known_exclusions":[],"conditions_summary":"## Impact\nAn attacker with write access to the git repository connected to an n8n Source Control configuration could commit a malicious Data Table JSON file containing a crafted column name. When an administrator performed a Source Control Pull, n8n imported the file and could lead to SQL injection on the internal PostgreSQL instance.\n\nExploitation requires all of the following conditions:\n- The n8n instance uses PostgreSQL as its database backend.\n- The Source Control feature is enabled and connected to a repository the attacker can write to.\n- An administrator triggers a Source Control Pull.\n\n## Patches\nThe issue has been fixed in n8n version 1.123.43, 2.20.7, and 2.21.1. Users should upgrade to this version or later to remediate the vulnerability.\n\n## Workarounds\nIf upgrading is not immediately possible, administrators should consider the following temporary mitigations:\n- Disable the Source Control feature if it is not actively required.\n- Restrict write access to the connected git repository to fully trusted users only.\n- Avoid pulling from repositories that may have been modified by untrusted parties.\n\nThese workarounds do not fully remediate the risk and should only be used ","public_affected_ranges":["< 1.123.43"]},{"certainty":"source_listed","source_ids":["sr-11f9d25e339a1431b99c0c087c5cb86a"],"technology":"n8n","known_exclusions":[],"conditions_summary":"## Impact\nAn attacker with write access to the git repository connected to an n8n Source Control configuration could commit a malicious Data Table JSON file containing a crafted column name. When an administrator performed a Source Control Pull, n8n imported the file and could lead to SQL injection on the internal PostgreSQL instance.\n\nExploitation requires all of the following conditions:\n- The n8n instance uses PostgreSQL as its database backend.\n- The Source Control feature is enabled and connected to a repository the attacker can write to.\n- An administrator triggers a Source Control Pull.\n\n## Patches\nThe issue has been fixed in n8n version 1.123.43, 2.20.7, and 2.21.1. Users should upgrade to this version or later to remediate the vulnerability.\n\n## Workarounds\nIf upgrading is not immediately possible, administrators should consider the following temporary mitigations:\n- Disable the Source Control feature if it is not actively required.\n- Restrict write access to the connected git repository to fully trusted users only.\n- Avoid pulling from repositories that may have been modified by untrusted parties.\n\nThese workarounds do not fully remediate the risk and should only be used ","public_affected_ranges":[">= 2.21.0, < 2.21.1"]},{"certainty":"source_listed","source_ids":["sr-11f9d25e339a1431b99c0c087c5cb86a"],"technology":"n8n","known_exclusions":[],"conditions_summary":"## Impact\nAn attacker with write access to the git repository connected to an n8n Source Control configuration could commit a malicious Data Table JSON file containing a crafted column name. When an administrator performed a Source Control Pull, n8n imported the file and could lead to SQL injection on the internal PostgreSQL instance.\n\nExploitation requires all of the following conditions:\n- The n8n instance uses PostgreSQL as its database backend.\n- The Source Control feature is enabled and connected to a repository the attacker can write to.\n- An administrator triggers a Source Control Pull.\n\n## Patches\nThe issue has been fixed in n8n version 1.123.43, 2.20.7, and 2.21.1. Users should upgrade to this version or later to remediate the vulnerability.\n\n## Workarounds\nIf upgrading is not immediately possible, administrators should consider the following temporary mitigations:\n- Disable the Source Control feature if it is not actively required.\n- Restrict write access to the connected git repository to fully trusted users only.\n- Avoid pulling from repositories that may have been modified by untrusted parties.\n\nThese workarounds do not fully remediate the risk and should only be used ","public_affected_ranges":[">= 2.0.0-rc.0, < 2.20.7"]}],"null_published_at":"2026-11-04T10:04:27.872Z","source_updated_at":"2026-07-20T13:41:03.000Z","source_disclosed_at":"2026-05-14T16:18:00.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-04T02:49:06.528Z"}],"next_cursor":null,"snapshot_revision":"42594"}