CVE-2026-19880 is a path traversal vulnerability in QOS.CH Sarl Logback-classic (logback-classic module) affecting versions from 0.9.14 through 1.6.2. The issue arises because an MDC-based discriminator value is not sanitized before being used in a nested FileAppender path, allowing an attacker who can influence this MDC value (for example, via an HTTP header) to create or append log files outside the intended directory. This vulnerability has a medium severity rating with a CVSS score of 6.3.
Trigger.dev versions from 4.4.2 up to but not including 4.5.0 contain a path traversal vulnerability in the packet presign routes. This flaw allows a caller-controlled filename to escape the intended restricted directory, enabling unauthorized read or overwrite access to other organizations' offloaded task payloads and outputs in multi-organization self-hosted instances. The vulnerability is fixed in version 4.5.0.
CVE-2026-73658 is a high-severity vulnerability in trigger.dev, a platform for building and deploying AI agents and workflows. Versions from 4.4.2 up to but not including 4.5.0-rc.5 have improper input validation in Aws4FetchClient methods that assign user-controlled keys to URL pathnames. This allows an attacker with a valid environment API key to bypass path normalization and obtain presigned URLs for other tenants' object-store keys, potentially reading or overwriting task payloads. The issue is fixed starting in version 4.5.0-rc.5. The vulnerability involves CWE-20 (Improper Input Validation), CWE-22 (Path Traversal), and CWE-862 (Missing Authorization).
Trigger.dev is a platform for building and deploying fully managed AI agents and workflows. From 4.4.2 until 4.5.0-rc.4, `POST /api/v1/runs/:runParam/replay` in apps/webapp/app/routes/api.v1.runs.$runParam.replay.ts uses `prisma.taskRun.findUnique({ where: { friendlyId: runParam } })` without a runtimeEnvironmentId filter, then ReplayTaskRunService in apps/webapp/app/v3/services/replayTaskRun.server.ts replays the selected run in the victim environment. Any valid environment API key can therefore replay another tenant's run by friendlyId, consuming victim resources and repeating side effects; when `payloadType: "application/store"` is used, overrideExistingPayloadPacket() calls conditionallyImportPacket() on existingTaskRun.payload without an integrity check, so payload bytes overwritten through a separate object-store path-traversal vulnerability become attacker-controlled input to the victim task. This issue is fixed in version 4.5.0-rc.4.
IBM Documentation Offline versions 1.0.0 through 1.4.1 contain a path traversal vulnerability that allows remote attackers to read arbitrary files. This occurs due to improper limitation of pathnames to restricted directories. The vulnerability has a high severity with a CVSS score of 7.5. No official patch or remediation guidance is currently provided by the vendor.
IBM i versions 7.3, 7.4, 7.5, and 7.6 contain a path traversal vulnerability (CWE-22) that could allow a remote authenticated attacker to access sensitive information. The vulnerability does not require user interaction and has a medium severity rating with a CVSS score of 4.3. No official patch or remediation guidance has been provided yet.
CVE-2026-17071 is a path traversal vulnerability in IBM i versions 7.3, 7.4, 7.5, and 7.6. It allows a remote authenticated attacker to perform unauthorized file manipulation by exploiting improper limitation of pathnames to restricted directories. The vulnerability has a low severity score and does not impact confidentiality or availability but can affect integrity.
CVE-2026-17043 is a path traversal vulnerability in IBM i versions 7.3, 7.4, 7.5, and 7.6 that allows a remote authenticated attacker to delete arbitrary files. The vulnerability arises from improper limitation of pathname to a restricted directory. The CVSS score is 3.8, indicating low severity. No official patch or remediation guidance is currently available. There are no known exploits in the wild at this time.
IBM i versions 7.3, 7.4, 7.5, and 7.6 contain a path traversal vulnerability (CWE-22) that could allow a remote authenticated attacker to gain unauthorized access to arbitrary objects. This vulnerability has a high severity with a CVSS score of 8.5, indicating significant impact on confidentiality, integrity, and availability. No official patch or remediation guidance has been provided yet.
A path traversal vulnerability (CWE-22) exists in compliance-trestle's profile import mechanism prior to versions 3.12.3 and 4.0.3. The vulnerability allows crafted OSCAL profile YAML files with malicious imports[].href values to read arbitrary files outside the intended workspace. The issue is fixed in versions 3.12.3 and 4.0.3.
WsgiDAV versions 4.3.3 and earlier contain a path traversal vulnerability that allows a WebDAV request path with an encoded parent-directory segment to escape the configured filesystem share root. This issue is resolved in version 4.3.4.
Vitest is a testing framework powered by Vite. Prior to versions 3.2.7, 4.1.10, and 5.0.0-beta.6, Browser Mode provider commands including upload, takeScreenshot, screenshotMatcher, stopChunkTrace, deleteTracing, and annotateTraces accept browser-supplied file paths without enforcing the allowWrite permission gate or confining paths to the project root. A client that can reach the Browser Mode API can read arbitrary local files, create or overwrite image and trace files, or delete files accessible to the Vitest process even when allowWrite is false. This issue is fixed in versions 3.2.7, 4.1.10, and 5.0.0-beta.6.
Data::MuForm::Localizer versions through 0.05 for Perl execute Perl from a message catalog header, reached at an arbitrary path because load_lexicon interpolates the language attribute into the catalog filename.
load_lexicon builds the catalog path by appending `Messages/$lang.po` to the directory holding Localizer.pm, where $lang is the language attribute, with no check that it names a bare locale tag. A value holding `../` segments walks out of the message directory, so any readable path with a `.po` suffix is loaded. While parsing the catalog, extract_header_msgstr takes the `Plural-Forms:` header, prefixes `$` to the bare words nplurals, plural and n, and passes the rest verbatim into a string that is evaluated: the nplurals form evaluates the header expression immediately, and the plural_code form compiles it into a subroutine whose body runs when a plural message is localized. A header of `nplurals=2; plural=(system('...'),0);` therefore runs that command as the catalog loads. The evaluation inherits strict, so an expression that assigns to an undeclared variable fails to compile, while one built from calls alone does not.
An application that sets the language attribute from request data, an Accept-Language header or a locale parameter, and an attacker who can place a file with a `.po` suffix and chosen contents at a readable path, together give code execution as the application user. The message expansion path is not affected: expand_named substitutes only the placeholder names the caller supplies, and _mangle_value returns the value unchanged.
A path traversal vulnerability exists in rsync versions 2.3.3 through 3.4.4. This flaw allows a malicious sender to escape the intended module root directory by exploiting symbolic links when using the --partial-dir or --backup-dir options. An attacker with write access to place or leverage symlinks can cause arbitrary file writes outside the module root.
OpenList a file list program that supports multiple storage. Prior to 4.2.4, the authenticated /api/fs/batch_rename handler in server/handles/fsbatch.go authorizes only the source directory produced by user.JoinPath(req.SrcDir) and validates renameObject.NewName with checkRelativePath, but does not validate attacker-controlled renameObject.SrcName, supplied as src_name, before concatenating it with the authorized path and passing the result to fs.Rename. A user with rename permission can use traversal segments in src_name to make path normalization select a file outside the authorized directory and configured base path, resulting in cross-user file integrity loss, limited availability impact, and file-existence disclosure through success or error responses. This issue is fixed in version 4.2.4.
MCP Atlassian is a Model Context Protocol (MCP) server for Atlassian products (Confluence and Jira). Prior to 0.22.0, confluence_upload_attachment passes its client-supplied file_path directly to open(file_path, "rb") in src/mcp_atlassian/confluence/attachments.py through _upload_attachment_direct() without calling validate_safe_path. An authenticated MCP client can read any file accessible to the server process and exfiltrate it to Confluence as an attachment. If an AI agent can be induced to call the tool through untrusted content, the same flaw can disclose server environment variables such as CONFLUENCE_API_TOKEN and other credentials. This issue is fixed in version 0.22.0.