Common Weakness Enumeration

CWE-22

Allowed-with-Review

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Abstraction: Base · Status: Stable

The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

16268 vulnerabilities reference this CWE, most recent first.

GHSA-VX2G-7GG2-2Q26

Vulnerability from github – Published: 2024-10-03 06:30 – Updated: 2024-10-03 06:30
VLAI
Details

The Social Web Suite – Social Media Auto Post, Social Media Auto Publish plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 4.1.11 via the download_log function. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2024-8352"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-22"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-10-03T04:15:04Z",
    "severity": "HIGH"
  },
  "details": "The Social Web Suite \u2013 Social Media Auto Post, Social Media Auto Publish plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 4.1.11 via the download_log function. This makes it possible for unauthenticated attackers to read the contents of arbitrary files on the server, which can contain sensitive information.",
  "id": "GHSA-vx2g-7gg2-2q26",
  "modified": "2024-10-03T06:30:34Z",
  "published": "2024-10-03T06:30:33Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-8352"
    },
    {
      "type": "WEB",
      "url": "https://plugins.trac.wordpress.org/browser/social-web-suite/trunk/includes/libs/class-socialwebsuite-log.php#L78"
    },
    {
      "type": "WEB",
      "url": "https://plugins.trac.wordpress.org/changeset/3155593/social-web-suite/trunk?old=3068377\u0026old_path=%2Fsocial-web-suite%2Ftrunk"
    },
    {
      "type": "WEB",
      "url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/78ba132c-b5b4-4999-a0ec-67d17ae2857f?source=cve"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-VX32-XF7G-9GHR

Vulnerability from github – Published: 2026-11-16 22:35 – Updated: 2026-11-16 22:35
VLAI
Summary
qbee-agent: Docker Compose build context Zip Slip writes outside context directory
Details

Summary

qbee-agent contains a Zip Slip vulnerability in app/utils/tar.go. The tar extractor checks whether an entry remains inside the destination directory with:

strings.HasPrefix(targetPath, destdirClean)

This does not enforce a path separator boundary. If the destination directory is /tmp/.../context, a tar entry such as ../context-outside/payload.txt cleans to /tmp/.../context-outside/payload.txt and still passes the prefix check. qbee-agent then creates the outside directory and writes the payload outside the intended extraction root.

The issue is reachable through the Docker Compose build context path when UseContext is enabled.

Details

Code references below were verified against qbee-io/qbee-agent commit:

  • 1d8bdbb7422adb4ca563d3114cbe2817d6ba3581

Affected repository:

  • qbee-io/qbee-agent

Affected files:

  • app/utils/tar.go
  • Docker Compose context path in app/configuration/bundle_docker_compose.go

The vulnerable extraction code:

  • app/utils/tar.go:89-93
targetPath := filepath.Clean(filepath.Join(destPath, header.Name))
destdirClean := filepath.Clean(destPath)

if !strings.HasPrefix(targetPath, destdirClean) {
    return fmt.Errorf("tar entry %s is outside of destination directory %s", targetPath, destdirClean)
}

The file is then created at the accepted targetPath:

  • app/utils/tar.go:96-109
case tar.TypeDir:
    if err := os.MkdirAll(targetPath, 0755); err != nil {
        return err
    }
case tar.TypeReg:
    targetFile, err := os.Create(targetPath)

Docker Compose build contexts reach this extractor:

  • app/configuration/bundle_docker_compose.go:238-270

The context archive is downloaded and then unpacked into the compose project context directory with utils.UnpackTar.

Archive source and role evidence:

  • app/configuration/compose.go:14 defines the Docker Compose build context as the remote configuration field Context string.
  • app/configuration/compose.go:26 enables this path with UseContext.
  • app/configuration/file_manager.go:240-246 and app/configuration/file_manager.go:281-287 show that context sources are resolved either from file:// local files or from the Qbee file-manager API.
  • Qbee's Docker Compose documentation lists "Build Context" as a Docker Compose configuration option: https://docs.qbee.io/configuration-docker-compose.html
  • Qbee's RBAC documentation separates configuration:manage from files:manage, and maps "Configure -> Modify configuration" to configuration:manage while "Files manager -> Write access" maps to files:manage: https://docs.qbee.io/account-users-and-roles.html
  • Qbee's CI/CD documentation describes using a dedicated Qbee user with a role restricted to configuration changes to push and commit deployment configuration: https://docs.qbee.io/tutorial-iot-container-deployment-with-ci-cd-devops.html

Trust-boundary requirement:

  • The vulnerable primitive is clear: qbee-agent writes a regular file outside the intended context extraction directory.
  • The security boundary is present when the archive supplier is less privileged than the local qbee-agent process and is not supposed to write arbitrary sibling files in qbee-agent's Docker Compose cache/project area.
  • The public code and documentation support this boundary for tenants that delegate configuration and/or file-manager access to limited users or CI automation.
  • If a deployment allows only full device/fleet administrators to provide Docker Compose context archives, the finding should be treated as hardening for that deployment.

PoC

Two failing regression tests add.

The utility-level test proves the extractor bug directly:

  • app/utils/tar_test.go:132
  • Test_TarZipSlipSiblingPrefixBypass

Command:

wsl -e sh -lc 'cd /mnt/c/Users/kwak0/Documents/Qbee/targets/qbee-agent; /mnt/c/Users/kwak0/Documents/Qbee/.tools/go1.26.4-linux/go/bin/go test ./app/utils -run Test_TarZipSlipSiblingPrefixBypass -count=1 -v'

Observed result:

=== RUN   Test_TarZipSlipSiblingPrefixBypass
    tar_test.go:169: expected unpackTar to reject sibling-prefix traversal archive
    tar_test.go:174: path traversal: payload was written outside destPath at /tmp/.../context-outside/payload.txt; got "zip-slip-sibling-prefix"
--- FAIL: Test_TarZipSlipSiblingPrefixBypass (0.00s)
FAIL

The Docker Compose bundle-path test proves reachability through Compose.getContext():

  • app/configuration/bundle_docker_compose_context_zip_slip_test.go:13
  • Test_ComposeContextRejectsSiblingPrefixZipSlip

Command:

wsl -e sh -lc 'cd /mnt/c/Users/kwak0/Documents/Qbee/targets/qbee-agent; /mnt/c/Users/kwak0/Documents/Qbee/.tools/go1.26.4-linux/go/bin/go test ./app/configuration -run Test_ComposeContextRejectsSiblingPrefixZipSlip -count=1 -v'

Observed result:

=== RUN   Test_ComposeContextRejectsSiblingPrefixZipSlip
    bundle_docker_compose_context_zip_slip_test.go:66: expected compose context unpack to reject sibling-prefix traversal archive
    bundle_docker_compose_context_zip_slip_test.go:75: compose context path traversal wrote outside context dir at /tmp/.../cache/docker_compose/project-a/context-outside/payload.txt; got "compose-context-zip-slip"
--- FAIL: Test_ComposeContextRejectsSiblingPrefixZipSlip (0.00s)
FAIL

Impact

An attacker-controlled Docker Compose build context archive can create directories and regular files outside qbee-agent's intended context extraction directory, with qbee-agent process privileges.

The demonstrated impact is constrained path traversal:

  • It can write sibling-prefix paths such as cache/docker_compose/<project>/context-outside/payload.txt.
  • It does not demonstrate writing arbitrary paths such as /etc/passwd; those do not pass the current string-prefix check.
  • It can corrupt or alter files in nearby qbee-agent Docker Compose cache/project paths if their cleaned path shares the destination prefix.
  • It may affect integrity or availability of qbee-agent-managed Docker Compose state, depending on the project/cache layout.

This report does not claim direct RCE.

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "go.qbee.io/agent"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "0.0.0-20260908095235-eb7875f0a849"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-129237"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-22"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-11-16T22:35:40Z",
    "nvd_published_at": "2026-11-16T17:17:31Z",
    "severity": "MODERATE"
  },
  "details": "## Summary\n\n`qbee-agent` contains a Zip Slip vulnerability in `app/utils/tar.go`. The tar extractor checks whether an entry remains inside the destination directory with:\n\n```go\nstrings.HasPrefix(targetPath, destdirClean)\n```\n\nThis does not enforce a path separator boundary. If the destination directory is `/tmp/.../context`, a tar entry such as `../context-outside/payload.txt` cleans to `/tmp/.../context-outside/payload.txt` and still passes the prefix check. qbee-agent then creates the outside directory and writes the payload outside the intended extraction root.\n\nThe issue is reachable through the Docker Compose build context path when `UseContext` is enabled.\n\n## Details\n\nCode references below were verified against `qbee-io/qbee-agent` commit:\n\n- `1d8bdbb7422adb4ca563d3114cbe2817d6ba3581`\n\nAffected repository:\n\n- `qbee-io/qbee-agent`\n\nAffected files:\n\n- `app/utils/tar.go`\n- Docker Compose context path in `app/configuration/bundle_docker_compose.go`\n\nThe vulnerable extraction code:\n\n- `app/utils/tar.go:89-93`\n\n```go\ntargetPath := filepath.Clean(filepath.Join(destPath, header.Name))\ndestdirClean := filepath.Clean(destPath)\n\nif !strings.HasPrefix(targetPath, destdirClean) {\n    return fmt.Errorf(\"tar entry %s is outside of destination directory %s\", targetPath, destdirClean)\n}\n```\n\nThe file is then created at the accepted `targetPath`:\n\n- `app/utils/tar.go:96-109`\n\n```go\ncase tar.TypeDir:\n    if err := os.MkdirAll(targetPath, 0755); err != nil {\n        return err\n    }\ncase tar.TypeReg:\n    targetFile, err := os.Create(targetPath)\n```\n\nDocker Compose build contexts reach this extractor:\n\n- `app/configuration/bundle_docker_compose.go:238-270`\n\nThe context archive is downloaded and then unpacked into the compose project context directory with `utils.UnpackTar`.\n\nArchive source and role evidence:\n\n- `app/configuration/compose.go:14` defines the Docker Compose build context as the remote configuration field `Context string`.\n- `app/configuration/compose.go:26` enables this path with `UseContext`.\n- `app/configuration/file_manager.go:240-246` and `app/configuration/file_manager.go:281-287` show that context sources are resolved either from `file://` local files or from the Qbee file-manager API.\n- Qbee\u0027s Docker Compose documentation lists \"Build Context\" as a Docker Compose configuration option: https://docs.qbee.io/configuration-docker-compose.html\n- Qbee\u0027s RBAC documentation separates `configuration:manage` from `files:manage`, and maps \"Configure -\u003e Modify configuration\" to `configuration:manage` while \"Files manager -\u003e Write access\" maps to `files:manage`: https://docs.qbee.io/account-users-and-roles.html\n- Qbee\u0027s CI/CD documentation describes using a dedicated Qbee user with a role restricted to configuration changes to push and commit deployment configuration: https://docs.qbee.io/tutorial-iot-container-deployment-with-ci-cd-devops.html\n\nTrust-boundary requirement:\n\n- The vulnerable primitive is clear: qbee-agent writes a regular file outside the intended context extraction directory.\n- The security boundary is present when the archive supplier is less privileged than the local qbee-agent process and is not supposed to write arbitrary sibling files in qbee-agent\u0027s Docker Compose cache/project area.\n- The public code and documentation support this boundary for tenants that delegate configuration and/or file-manager access to limited users or CI automation.\n- If a deployment allows only full device/fleet administrators to provide Docker Compose context archives, the finding should be treated as hardening for that deployment.\n\n## PoC\n\nTwo failing regression tests add.\n\nThe utility-level test proves the extractor bug directly:\n\n- `app/utils/tar_test.go:132`\n- `Test_TarZipSlipSiblingPrefixBypass`\n\nCommand:\n\n```sh\nwsl -e sh -lc \u0027cd /mnt/c/Users/kwak0/Documents/Qbee/targets/qbee-agent; /mnt/c/Users/kwak0/Documents/Qbee/.tools/go1.26.4-linux/go/bin/go test ./app/utils -run Test_TarZipSlipSiblingPrefixBypass -count=1 -v\u0027\n```\n\nObserved result:\n\n```text\n=== RUN   Test_TarZipSlipSiblingPrefixBypass\n    tar_test.go:169: expected unpackTar to reject sibling-prefix traversal archive\n    tar_test.go:174: path traversal: payload was written outside destPath at /tmp/.../context-outside/payload.txt; got \"zip-slip-sibling-prefix\"\n--- FAIL: Test_TarZipSlipSiblingPrefixBypass (0.00s)\nFAIL\n```\n\nThe Docker Compose bundle-path test proves reachability through `Compose.getContext()`:\n\n- `app/configuration/bundle_docker_compose_context_zip_slip_test.go:13`\n- `Test_ComposeContextRejectsSiblingPrefixZipSlip`\n\nCommand:\n\n```sh\nwsl -e sh -lc \u0027cd /mnt/c/Users/kwak0/Documents/Qbee/targets/qbee-agent; /mnt/c/Users/kwak0/Documents/Qbee/.tools/go1.26.4-linux/go/bin/go test ./app/configuration -run Test_ComposeContextRejectsSiblingPrefixZipSlip -count=1 -v\u0027\n```\n\nObserved result:\n\n```text\n=== RUN   Test_ComposeContextRejectsSiblingPrefixZipSlip\n    bundle_docker_compose_context_zip_slip_test.go:66: expected compose context unpack to reject sibling-prefix traversal archive\n    bundle_docker_compose_context_zip_slip_test.go:75: compose context path traversal wrote outside context dir at /tmp/.../cache/docker_compose/project-a/context-outside/payload.txt; got \"compose-context-zip-slip\"\n--- FAIL: Test_ComposeContextRejectsSiblingPrefixZipSlip (0.00s)\nFAIL\n```\n\n## Impact\n\nAn attacker-controlled Docker Compose build context archive can create directories and regular files outside qbee-agent\u0027s intended context extraction directory, with qbee-agent process privileges.\n\nThe demonstrated impact is constrained path traversal:\n\n- It can write sibling-prefix paths such as `cache/docker_compose/\u003cproject\u003e/context-outside/payload.txt`.\n- It does not demonstrate writing arbitrary paths such as `/etc/passwd`; those do not pass the current string-prefix check.\n- It can corrupt or alter files in nearby qbee-agent Docker Compose cache/project paths if their cleaned path shares the destination prefix.\n- It may affect integrity or availability of qbee-agent-managed Docker Compose state, depending on the project/cache layout.\n\nThis report does not claim direct RCE.",
  "id": "GHSA-vx32-xf7g-9ghr",
  "modified": "2026-11-16T22:35:40Z",
  "published": "2026-11-16T22:35:40Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/qbee-io/qbee-agent/security/advisories/GHSA-vx32-xf7g-9ghr"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-129237"
    },
    {
      "type": "WEB",
      "url": "https://github.com/qbee-io/qbee-agent/pull/148"
    },
    {
      "type": "WEB",
      "url": "https://github.com/qbee-io/qbee-agent/commit/eb7875f0a849cb33325956d0b75e27061d7a7fa3"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/qbee-io/qbee-agent"
    },
    {
      "type": "WEB",
      "url": "https://github.com/qbee-io/qbee-agent/releases/tag/2026.41"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L",
      "type": "CVSS_V3"
    }
  ],
  "summary": "qbee-agent: Docker Compose build context Zip Slip writes outside context directory"
}

GHSA-VX4H-HW7F-47C3

Vulnerability from github – Published: 2024-07-09 15:30 – Updated: 2024-07-09 15:30
VLAI
Details

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Themewinter WPCafe allows Path Traversal.This issue affects WPCafe: from n/a through 2.2.27.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2024-37513"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-22"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-07-09T13:15:10Z",
    "severity": "HIGH"
  },
  "details": "Improper Limitation of a Pathname to a Restricted Directory (\u0027Path Traversal\u0027) vulnerability in Themewinter WPCafe allows Path Traversal.This issue affects WPCafe: from n/a through 2.2.27.",
  "id": "GHSA-vx4h-hw7f-47c3",
  "modified": "2024-07-09T15:30:53Z",
  "published": "2024-07-09T15:30:53Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-37513"
    },
    {
      "type": "WEB",
      "url": "https://patchstack.com/database/vulnerability/wp-cafe/wordpress-wpcafe-plugin-2-2-27-local-file-inclusion-vulnerability?_s_id=cve"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-VX4P-X4MC-MG7C

Vulnerability from github – Published: 2022-05-24 16:57 – Updated: 2022-12-07 21:30
VLAI
Details

IBM Sterling File Gateway 2.2.0.0 through 6.0.1.0 could allow a remote attacker to traverse directories on the system. An attacker could send a specially-crafted URL request containing "dot dot" sequences (/../) to view arbitrary files on the system. IBM X-Force ID: 162769.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2019-4423"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-22"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2019-09-30T16:15:00Z",
    "severity": "MODERATE"
  },
  "details": "IBM Sterling File Gateway 2.2.0.0 through 6.0.1.0 could allow a remote attacker to traverse directories on the system. An attacker could send a specially-crafted URL request containing \"dot dot\" sequences (/../) to view arbitrary files on the system. IBM X-Force ID: 162769.",
  "id": "GHSA-vx4p-x4mc-mg7c",
  "modified": "2022-12-07T21:30:28Z",
  "published": "2022-05-24T16:57:15Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2019-4423"
    },
    {
      "type": "WEB",
      "url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/162769"
    },
    {
      "type": "WEB",
      "url": "https://www.ibm.com/support/pages/node/957207"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-VX59-6637-4544

Vulnerability from github – Published: 2022-05-01 18:36 – Updated: 2022-05-01 18:36
VLAI
Details

Directory traversal vulnerability in the WML engine preprocessor for Wesnoth 1.2.x before 1.2.8, and 1.3.x before 1.3.12, allows remote attackers to read arbitrary files via ".." sequences in unknown vectors.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2007-5742"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-22"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2007-12-01T06:46:00Z",
    "severity": "HIGH"
  },
  "details": "Directory traversal vulnerability in the WML engine preprocessor for Wesnoth 1.2.x before 1.2.8, and 1.3.x before 1.3.12, allows remote attackers to read arbitrary files via \"..\" sequences in unknown vectors.",
  "id": "GHSA-vx59-6637-4544",
  "modified": "2022-05-01T18:36:14Z",
  "published": "2022-05-01T18:36:14Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2007-5742"
    },
    {
      "type": "WEB",
      "url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/38752"
    },
    {
      "type": "WEB",
      "url": "https://www.redhat.com/archives/fedora-package-announce/2007-December/msg00004.html"
    },
    {
      "type": "WEB",
      "url": "https://www.redhat.com/archives/fedora-package-announce/2007-December/msg00006.html"
    },
    {
      "type": "WEB",
      "url": "http://osvdb.org/41713"
    },
    {
      "type": "WEB",
      "url": "http://secunia.com/advisories/27786"
    },
    {
      "type": "WEB",
      "url": "http://secunia.com/advisories/27920"
    },
    {
      "type": "WEB",
      "url": "http://secunia.com/advisories/27943"
    },
    {
      "type": "WEB",
      "url": "http://sourceforge.net/project/shownotes.php?release_id=557098"
    },
    {
      "type": "WEB",
      "url": "http://www.debian.org/security/2007/dsa-1421"
    },
    {
      "type": "WEB",
      "url": "http://www.securityfocus.com/bid/26626"
    },
    {
      "type": "WEB",
      "url": "http://www.vupen.com/english/advisories/2007/4026"
    },
    {
      "type": "WEB",
      "url": "http://www.wesnoth.org/forum/viewtopic.php?p=264289#264289"
    },
    {
      "type": "WEB",
      "url": "http://www.wesnoth.org/forum/viewtopic.php?t=18844"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

GHSA-VX5W-CXCH-WWC9

Vulnerability from github – Published: 2020-09-03 19:02 – Updated: 2020-08-31 18:46
VLAI
Summary
Path Traversal in f-serv
Details

All versions of f-serv are vulnerable to Path Traversal. Due to insufficient input sanitization in URLs, attackers can access server files by using relative paths when fetching files.

Recommendation

No fix is currently available. Consider using an alternative package until a fix is made available.

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "f-serv"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0.0.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [],
  "database_specific": {
    "cwe_ids": [
      "CWE-22"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2020-08-31T18:46:58Z",
    "nvd_published_at": null,
    "severity": "CRITICAL"
  },
  "details": "All versions of `f-serv` are vulnerable to Path Traversal.  Due to insufficient input sanitization in URLs, attackers can access server files by using relative paths when fetching files. \n\n\n## Recommendation\n\nNo fix is currently available. Consider using an alternative package until a fix is made available.",
  "id": "GHSA-vx5w-cxch-wwc9",
  "modified": "2020-08-31T18:46:58Z",
  "published": "2020-09-03T19:02:27Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://www.npmjs.com/advisories/1092"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [],
  "summary": "Path Traversal in f-serv"
}

GHSA-VX5X-2G22-WQJR

Vulnerability from github – Published: 2026-08-11 15:32 – Updated: 2026-09-01 21:31
VLAI
Details

n8n versions before 1.123.67 contain a path traversal vulnerability in the Git node's fetch, pull, and push-tags operations that allows authenticated users to bypass repository-path containment checks. Attackers with workflow create/execute rights can point allowlisted remote configurations at local paths outside the sandbox to pull arbitrary git repositories and read their files and history.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-72770"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-22"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-08-11T13:19:07Z",
    "severity": "HIGH"
  },
  "details": "n8n versions before 1.123.67 contain a path traversal vulnerability in the Git node\u0027s fetch, pull, and push-tags operations that allows authenticated users to bypass repository-path containment checks. Attackers with workflow create/execute rights can point allowlisted remote configurations at local paths outside the sandbox to pull arbitrary git repositories and read their files and history.",
  "id": "GHSA-vx5x-2g22-wqjr",
  "modified": "2026-09-01T21:31:17Z",
  "published": "2026-08-11T15:32:37Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/n8n-io/n8n/security/advisories/GHSA-gf29-4f56-r2jf"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-72770"
    },
    {
      "type": "WEB",
      "url": "https://www.vulncheck.com/advisories/n8n-before-path-traversal-via-git-node-operations"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
      "type": "CVSS_V3"
    },
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
      "type": "CVSS_V4"
    }
  ]
}

GHSA-VX64-9PHG-MMPV

Vulnerability from github – Published: 2023-07-11 18:31 – Updated: 2024-04-04 05:57
VLAI
Details

An improper limitation of a pathname to a restricted directory ('Path Traversal') vulnerability [CWE-22] in FortiExtender management interface 7.0.0 through 7.0.3, 4.2.0 through 4.2.4, 4.1.1 through 4.1.8, 4.0.0 through 4.0.2, 3.3.0 through 3.3.2, 3.2.1 through 3.2.3, 5.3 all versions may allow an unauthenticated and remote attacker to retrieve arbitrary files from the underlying filesystem via specially crafted web requests.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2022-23447"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-22"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2023-07-11T17:15:10Z",
    "severity": "HIGH"
  },
  "details": "An improper limitation of a pathname to a restricted directory (\u0027Path Traversal\u0027) vulnerability [CWE-22] in FortiExtender management interface  7.0.0 through 7.0.3, 4.2.0 through 4.2.4, 4.1.1 through 4.1.8, 4.0.0 through 4.0.2, 3.3.0 through 3.3.2, 3.2.1 through 3.2.3, 5.3 all versions may allow an unauthenticated and remote attacker to retrieve\u00a0arbitrary files from the underlying filesystem via specially crafted web requests.",
  "id": "GHSA-vx64-9phg-mmpv",
  "modified": "2024-04-04T05:57:00Z",
  "published": "2023-07-11T18:31:22Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2022-23447"
    },
    {
      "type": "WEB",
      "url": "https://fortiguard.com/psirt/FG-IR-22-039"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-VX68-WHC5-QV39

Vulnerability from github – Published: 2022-05-01 18:29 – Updated: 2022-05-01 18:29
VLAI
Details

Directory traversal vulnerability in rxRPC.dll in CA (Computer Associates) BrightStor ARCserve Backup for Laptops and Desktops r11.0 through r11.5 allows remote attackers to upload and overwrite arbitrary files via a ..\ (dot dot backslash) sequence in the destination filename argument to sub-function 8 in the rxrReceiveFileFromServer command.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2007-5005"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-22"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2007-10-01T20:17:00Z",
    "severity": "HIGH"
  },
  "details": "Directory traversal vulnerability in rxRPC.dll in CA (Computer Associates) BrightStor ARCserve Backup for Laptops and Desktops r11.0 through r11.5 allows remote attackers to upload and overwrite arbitrary files via a ..\\ (dot dot backslash) sequence in the destination filename argument to sub-function 8 in the rxrReceiveFileFromServer command.",
  "id": "GHSA-vx68-whc5-qv39",
  "modified": "2022-05-01T18:29:04Z",
  "published": "2022-05-01T18:29:04Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2007-5005"
    },
    {
      "type": "WEB",
      "url": "http://research.eeye.com/html/advisories/published/AD20070920.html"
    },
    {
      "type": "WEB",
      "url": "http://secunia.com/advisories/25606"
    },
    {
      "type": "WEB",
      "url": "http://supportconnectw.ca.com/public/sams/lifeguard/infodocs/caarcservebld-securitynotice.asp"
    },
    {
      "type": "WEB",
      "url": "http://www.ca.com/us/securityadvisor/newsinfo/collateral.aspx?cid=156006"
    },
    {
      "type": "WEB",
      "url": "http://www.ca.com/us/securityadvisor/vulninfo/vuln.aspx?id=35676"
    },
    {
      "type": "WEB",
      "url": "http://www.securityfocus.com/archive/1/480252/100/100/threaded"
    },
    {
      "type": "WEB",
      "url": "http://www.securityfocus.com/bid/24348"
    },
    {
      "type": "WEB",
      "url": "http://www.securitytracker.com/id?1018728"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

GHSA-VX6J-PJRH-VGJH

Vulnerability from github – Published: 2021-12-15 22:54 – Updated: 2021-12-15 22:27
VLAI
Summary
PHP file inclusion in the Sulu admin panel
Details

Impact

What kind of vulnerability is it? Who is impacted?

An attacker can read arbitrary local files via a PHP file include. In a default configuration this also leads to remote code execution.

  • Compromised components: Arbitrary file read on the server, (Potential) Remote code execution
  • Exploitation pre-requisite: User account on the backend

Patches

Has the problem been patched? What versions should users upgrade to?

The problem is patched with the Versions 1.6.44, 2.2.18, 2.3.8, 2.4.0

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

Overwrite the service sulu_route.generator.expression_token_provider and wrap the translator before passing it to the expression language.

References

Are there any links users can visit to find out more?

Currently not.

For more information

If you have any questions or comments about this advisory: * Open an issue in example link to repo * Email us at example email address

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "Packagist",
        "name": "sulu/sulu"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.6.44"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Packagist",
        "name": "sulu/sulu"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "2.0.0"
            },
            {
              "fixed": "2.2.18"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Packagist",
        "name": "sulu/sulu"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "2.3.0"
            },
            {
              "fixed": "2.3.8"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Packagist",
        "name": "sulu/sulu"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "2.4.0-RC1"
            },
            {
              "fixed": "2.4.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "2.4.0-RC1"
      ]
    }
  ],
  "aliases": [
    "CVE-2021-43836"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-22"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2021-12-15T22:27:31Z",
    "nvd_published_at": "2021-12-15T20:15:00Z",
    "severity": "HIGH"
  },
  "details": "### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\nAn attacker can read arbitrary local files via a PHP file include. In a default configuration this also leads to remote code execution.\n\n* Compromised components: Arbitrary file read on the server, (Potential) Remote code execution\n* Exploitation pre-requisite: User account on the backend\n\n### Patches\n\n_Has the problem been patched? What versions should users upgrade to?_\n\nThe problem is patched with the Versions 1.6.44, 2.2.18, 2.3.8, 2.4.0\n\n### Workarounds\n\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\nOverwrite the service `sulu_route.generator.expression_token_provider` and wrap the translator before passing it to the expression language. \n\n### References\n\n_Are there any links users can visit to find out more?_\n\nCurrently not.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Open an issue in [example link to repo](http://example.com)\n* Email us at [example email address](mailto:example@example.com)\n",
  "id": "GHSA-vx6j-pjrh-vgjh",
  "modified": "2021-12-15T22:27:31Z",
  "published": "2021-12-15T22:54:20Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/sulu/sulu/security/advisories/GHSA-vx6j-pjrh-vgjh"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2021-43836"
    },
    {
      "type": "WEB",
      "url": "https://github.com/sulu/sulu/commit/9c948f9ce350c68b53af8c3910e2cefc7f722b54"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/sulu/sulu"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "PHP file inclusion in the Sulu admin panel"
}

Mitigation MIT-5.1
Implementation

Strategy: Input Validation

  • Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
  • When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."
  • Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
  • When validating filenames, use stringent allowlists that limit the character set to be used. If feasible, only allow a single "." character in the filename to avoid weaknesses such as CWE-23, and exclude directory separators such as "/" to avoid CWE-36. Use a list of allowable file extensions, which will help to avoid CWE-434.
  • Do not rely exclusively on a filtering mechanism that removes potentially dangerous characters. This is equivalent to a denylist, which may be incomplete (CWE-184). For example, filtering "/" is insufficient protection if the filesystem also supports the use of "\" as a directory separator. Another possible error could occur when the filtering is applied in a way that still produces dangerous data (CWE-182). For example, if "../" sequences are removed from the ".../...//" string in a sequential fashion, two instances of "../" would be removed from the original string, but the remaining characters would still form the "../" string.
Mitigation MIT-15
Architecture and Design

For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.

Mitigation MIT-20.1
Implementation

Strategy: Input Validation

  • Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.
  • Use a built-in path canonicalization function (such as realpath() in C) that produces the canonical version of the pathname, which effectively removes ".." sequences and symbolic links (CWE-23, CWE-59). This includes:
  • realpath() in C
  • getCanonicalPath() in Java
  • GetFullPath() in ASP.NET
  • realpath() or abs_path() in Perl
  • realpath() in PHP
Mitigation MIT-4
Architecture and Design

Strategy: Libraries or Frameworks

Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482].

Mitigation MIT-29
Operation

Strategy: Firewall

Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth [REF-1481].

Mitigation MIT-17
Architecture and Design Operation

Strategy: Environment Hardening

Run your code using the lowest privileges that are required to accomplish the necessary tasks [REF-76]. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.

Mitigation MIT-21.1
Architecture and Design

Strategy: Enforcement by Conversion

  • When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
  • For example, ID 1 could map to "inbox.txt" and ID 2 could map to "profile.txt". Features such as the ESAPI AccessReferenceMap [REF-185] provide this capability.
Mitigation MIT-22
Architecture and Design Operation

Strategy: Sandbox or Jail

  • Run the code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software.
  • OS-level examples include the Unix chroot jail, AppArmor, and SELinux. In general, managed code may provide some protection. For example, java.io.FilePermission in the Java SecurityManager allows the software to specify restrictions on file operations.
  • This may not be a feasible solution, and it only limits the impact to the operating system; the rest of the application may still be subject to compromise.
  • Be careful to avoid CWE-243 and other weaknesses related to jails.
Mitigation MIT-34
Architecture and Design Operation

Strategy: Attack Surface Reduction

  • Store library, include, and utility files outside of the web document root, if possible. Otherwise, store them in a separate directory and use the web server's access control capabilities to prevent attackers from directly requesting them. One common practice is to define a fixed constant in each calling program, then check for the existence of the constant in the library/include file; if the constant does not exist, then the file was directly requested, and it can exit immediately.
  • This significantly reduces the chance of an attacker being able to bypass any protection mechanisms that are in the base program but not in the include files. It will also reduce the attack surface.
Mitigation MIT-39
Implementation
  • Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended). The messages should not reveal the methods that were used to determine the error. Attackers can use detailed information to refine or optimize their original attack, thereby increasing their chances of success.
  • If errors must be captured in some detail, record them in log messages, but consider what could occur if the log messages can be viewed by attackers. Highly sensitive information such as passwords should never be saved to log files.
  • Avoid inconsistent messaging that might accidentally tip off an attacker about internal state, such as whether a user account exists or not.
  • In the context of path traversal, error messages which disclose path information can help attackers craft the appropriate attack strings to move through the file system hierarchy.
Mitigation MIT-16
Operation Implementation

Strategy: Environment Hardening

When using PHP, configure the application so that it does not use register_globals. During implementation, develop the application so that it does not rely on this feature, but be wary of implementing a register_globals emulation that is subject to weaknesses such as CWE-95, CWE-621, and similar issues.

CAPEC-126: Path Traversal

An adversary uses path manipulation methods to exploit insufficient input validation of a target to obtain access to data that should be not be retrievable by ordinary well-formed requests. A typical variety of this attack involves specifying a path to a desired file together with dot-dot-slash characters, resulting in the file access API or function traversing out of the intended directory structure and into the root file system. By replacing or modifying the expected path information the access function or API retrieves the file desired by the attacker. These attacks either involve the attacker providing a complete path to a targeted file or using control characters (e.g. path separators (/ or \) and/or dots (.)) to reach desired directories or files.

CAPEC-64: Using Slashes and URL Encoding Combined to Bypass Validation Logic

This attack targets the encoding of the URL combined with the encoding of the slash characters. An attacker can take advantage of the multiple ways of encoding a URL and abuse the interpretation of the URL. A URL may contain special character that need special syntax handling in order to be interpreted. Special characters are represented using a percentage character followed by two digits representing the octet code of the original character (%HEX-CODE). For instance US-ASCII space character would be represented with %20. This is often referred as escaped ending or percent-encoding. Since the server decodes the URL from the requests, it may restrict the access to some URL paths by validating and filtering out the URL requests it received. An attacker will try to craft an URL with a sequence of special characters which once interpreted by the server will be equivalent to a forbidden URL. It can be difficult to protect against this attack since the URL can contain other format of encoding such as UTF-8 encoding, Unicode-encoding, etc.

CAPEC-76: Manipulating Web Input to File System Calls

An attacker manipulates inputs to the target software which the target software passes to file system calls in the OS. The goal is to gain access to, and perhaps modify, areas of the file system that the target software did not intend to be accessible.

CAPEC-78: Using Escaped Slashes in Alternate Encoding

This attack targets the use of the backslash in alternate encoding. An adversary can provide a backslash as a leading character and causes a parser to believe that the next character is special. This is called an escape. By using that trick, the adversary tries to exploit alternate ways to encode the same character which leads to filter problems and opens avenues to attack.

CAPEC-79: Using Slashes in Alternate Encoding

This attack targets the encoding of the Slash characters. An adversary would try to exploit common filtering problems related to the use of the slashes characters to gain access to resources on the target host. Directory-driven systems, such as file systems and databases, typically use the slash character to indicate traversal between directories or other container components. For murky historical reasons, PCs (and, as a result, Microsoft OSs) choose to use a backslash, whereas the UNIX world typically makes use of the forward slash. The schizophrenic result is that many MS-based systems are required to understand both forms of the slash. This gives the adversary many opportunities to discover and abuse a number of common filtering problems. The goal of this pattern is to discover server software that only applies filters to one version, but not the other.