Path Traversal
Monthly
Path traversal in the web management interface of Tektronix 3 Series MDO oscilloscopes running firmware before 1.21.1 lets remote attackers read arbitrary files accessible to the web application by supplying insufficiently validated file paths. The flaw is rated CVSS 3.1 7.5 (AV:N/AC:L/PR:N/UI:N, C:H/I:N/A:N), but unauthenticated exploitation depends on device configuration - deployments that require login to the web interface reduce the practical risk to authenticated users. Impact is limited to confidentiality (file reads, no write or code execution); no public exploit code or confirmed active exploitation was identified at time of analysis, and exposure is bounded by these instruments typically residing on isolated lab networks rather than the internet.
Path traversal in the SCPI FILESystem command interface of Tektronix 3 Series MDO oscilloscopes running firmware before 1.21.1 allows authenticated remote attackers to read or modify arbitrary files on the device. The vulnerability arises from insufficient validation of file paths supplied to filesystem access commands and is rated CVSS 8.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N). No public exploit code or confirmed active exploitation (CISA KEV) has been identified at time of analysis, and exposure is typically limited because the SCPI interface is usually confined to lab or test networks rather than the public internet.
Unauthenticated path traversal in Countly Server before 24.05.50 and 25.03.44 lets remote attackers read arbitrary files that are readable by the server process, by abusing wildcard routes that serve public images and screenshots. The flaw affects deployments configured with the local filesystem backend of countlyFs (api/utils/countlyFs.js) - installs using the GridFS/database backend cannot be reached through these routes - and carries a CVSS 3.1 score of 7.5 (AV:N/AC:L/PR:N/UI:N/C:H/I:N/A:N), so no credentials, privileges, or user interaction are required. Impact is limited to file disclosure (no integrity or availability effect); vendor-released patches exist in 24.05.50 and 25.03.44, and no public exploit identified at time of analysis.
Arbitrary file and directory deletion in Countly Server (versions prior to 24.05.50 and 25.03.44) allows an authenticated user holding data-migration permission to pass a crafted exportid to the migration-deletion route and recursively remove any file or directory tree writable by the Countly server process, resulting in data loss and service disruption. The root issue is a path-traversal flaw (CWE-22) in plugins/data_migration/api/api.js in which the user-controlled exportid reaches clean_up_data in data_migration_helper.js without the sanitizeFilename-based containment checks introduced by the fix. The assessed CVSS 3.1 vector is AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H (base 8.1), confirming a network-reachable, low-complexity attack requiring an authenticated account (PR:L) with no user interaction, with high integrity and availability impact but no confidentiality exposure; no public exploit code was identified at time of analysis and there is no confirmed active exploitation (not in CISA KEV). Vendor fixes are available in 24.05.50 and 25.03.44.
Authenticated path traversal in Thermo Fisher Torrent Suite Software lets a user who already holds a valid low-privilege session on the Torrent Server web interface read arbitrary files that are accessible to the web service account. Per the assessed CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N), impact is confidentiality-only - no write, integrity, or code-execution effect - and the readable scope is bounded by the filesystem permissions of the web service account, so it cannot reach files that account cannot access. No public exploit code or confirmed active exploitation was identified at time of analysis, and the authentication prerequisite confines realistic risk to insiders or attackers who have already obtained credentials; this is a moderate-priority information-disclosure issue rather than a critical emergency. CISA published an ICS medical advisory (ICSMA-26-288-01) covering this flaw.
Unauthenticated path traversal in the 10Web Booster WordPress plugin (versions up to and including 2.34.5) lets remote attackers create arbitrary directories outside the plugin's cache root, with 0777 permissions applied recursively, and plant a cached page inside them by feeding unsanitized GET parameter names and values into the cache path. The write primitive is strictly limited - the filename is hard-coded to source.html and the body is the server-rendered page buffer rather than attacker-supplied content, so no executable file can be planted and code execution is not achievable, with the realistic outcomes being cache poisoning and stray directory creation (published CVSS 7.5 with I:H; the independent assessment revises integrity impact to Low), and no public exploit identified at time of analysis.
Arbitrary file deletion in the Groundhogg CRM, Newsletters and Marketing Automation plugin for WordPress (all versions up to and including 4.9.3) lets an authenticated user who holds the plugin's import_contacts capability - granted by default to Groundhogg's custom Sales Representative role - name an arbitrary server-side path and have the plugin delete it, with a realistic escalation to remote code execution (for example by removing wp-config.php). The flaw is reachable through the contact-import (CSV), REST API, and webhook paths that call copy_file, and it received a CVSS of 8.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H); there is no CISA KEV listing and no public exploit code identified at time of analysis. The practical risk is bounded by the authentication requirement and by the attacker's need to know or guess the absolute path of a valuable target, but the capability is assigned by default and no user interaction or non-default configuration is needed, making this a credible, actionable priority rather than an inflated high-CVSS issue.
Path traversal in WildFly's management take-snapshot operation lets an authenticated user holding only the Monitor RBAC role write a copy of the server configuration to an arbitrary filesystem location and then read it back, bypassing RBAC restrictions to disclose sensitive credentials. This is a credible, moderate-priority privilege-boundary bypass rather than a critical internet-facing threat, because exploitation requires an authenticated management session and a reachable management endpoint; no public exploit code has been identified at time of analysis and no vendor-released patch version is specified in the provided data.
Authenticated remote code execution is possible in Microsoft SharePoint Server Subscription Edition due to a path traversal flaw (CWE-22) that permits an attacker with low-privilege credentials to escape restricted directories and execute code over the network. The vulnerability carries a CVSS score of 8.8 (AV:N/AC:L/PR:L/UI:N) and requires a valid SharePoint session, making it a credible priority for patching but not an immediate emergency according to current evidence. A vendor patch is available, and no public exploit code has been identified at time of analysis.
Unauthenticated path-traversal file writes in the EnergizeLab Eilik and EilikO AI skill upload endpoint allow any remote attacker who can reach the FastAPI AI inference and profiling service to write arbitrary files on the robot's host system by supplying crafted traversal filenames in an upload request. Because the endpoint enforces neither authentication nor path constraints, exploitation is a straightforward, low-complexity primitive that lets an attacker tamper with the AI skill files the robots execute, degrading or subverting robot behavior and causing high integrity and availability impact (CVSS 3.1 base 9.1, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H, CWE-434); confidentiality is assessed as unaffected. The practical limiting factor is network reachability rather than credentials or configuration - these are consumer robots whose service is normally confined to the local network segment, so real-world exposure is materially narrower than the AV:N vector implies, and no public exploit code or confirmed active exploitation was identified at time of analysis (the flaw itself needs no user interaction or non-default toggle once the endpoint is reachable).
Absolute plot names passed to MatplotlibDataset.save() in kedro-datasets 9.3.0 through 9.6.0 let an authenticated user with the ability to influence plot-name keys write files outside the configured dataset directory, overwriting or creating files anywhere the Kedro process has write access. The flaw is rooted in validate_sub_path(), which strips leading slashes before validation, combined with pathlib join semantics that discard the base path whenever the supplied sub-path is absolute (POSIX '/outside.png', Windows 'C:\\outside.png', or UNC '\\\\server\\share\\outside.png'). Integrity impact is rated High (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N; CVSS 4.0 base 7.1), no public exploit code has been identified at time of analysis, and no CISA KEV entry exists; exploitability is gated by the attacker's ability to inject the plot-name keys (e.g., through untrusted input data or catalog configuration) and by the write permissions of the process running Kedro.
Path traversal in NetLicensing MCP Server versions prior to 0.1.8 allows an authenticated MCP client holding a valid but non-administrative NetLicensing API key to redirect the netlicensing_get_product lookup away from the intended product endpoint and onto the /token endpoint by supplying '../token' (or percent-encoded equivalents such as '..%2ftoken') as the product_number. Because the traversed response is serialized through the generic _wrap_json wrapper instead of _wrap_json_token_read, the redact_token_read() masking of APIKEY 'number' and SHOP 'shopURL' fields never runs, so plaintext token values - including admin-level credentials if present in the account - are returned in the tool output. No vendor patch is available below 0.1.8, where the issue is fixed; it is a confirmed privilege-escalation-by-credential-disclosure vector rather than direct code execution, and no public exploit has been identified at time of analysis beyond the exact payload documented in the vendor advisory.
Authenticated path traversal in Lychee photo-management tool prior to 7.6.4 allows any logged-in user to read files accessible to the web process - including the application's .env file with APP_KEY and database credentials, and other users' private images - by sending encoded traversal segments to GET /image/{path}. Exploitation is not unconditional: it requires the supported but non-default configuration with temporary_image_link_enabled on and both temporary_image_link_when_logged_in and secure_image_link_enabled off, so default installations do not expose the vulnerable code path in an exploitable state. The impact is read-only information disclosure (no write or availability effect) and disclosure of APP_KEY or DB credentials can escalate to further compromise; no public exploit was identified at time of analysis, and the vendor fixed the flaw in 7.6.4.
Path traversal in wildfly-core's deployment content handler allows an authenticated JBoss EAP, WildFly, Fuse 7, or Single Sign-On 7 user who holds the Deployer RBAC role to escape the restricted deployment directory and create files with attacker-controlled content or delete arbitrary directories on the server, escalating to full management SuperUser privileges. Exploitation requires that the Deployer role be delegated to the attacker (CVSS vector shows PR:L - authenticated, not anonymous) plus a crafted deployment name containing traversal sequences; environments that reserve the Deployer role for fully trusted administrators face little practical exposure. No public exploit code was identified at time of analysis and the flaw is not listed in CISA KEV, so this is a credible, actionable priority rather than an emergency.
Unauthenticated path traversal in the report blob endpoint of JetBrains Datalore before version 2026.2.1 allows a remote attacker who can reach the service to read arbitrary files accessible to the Datalore process. Per the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, base 7.5 HIGH), exploitation requires no credentials and no user interaction, making exposure the primary limiting factor: only network-reachable instances below 2026.2.1 are at risk, and the flaw yields confidentiality loss only, with no integrity or availability impact and no code execution on its own. There is no CISA KEV listing and no public exploit code identified at time of analysis, though the low-complexity, unauthenticated nature of the bug makes it an attractive target for opportunistic scanning of internet-facing deployments.
Root-level code execution on OPNsense firewalls running versions prior to 26.1.11 is achievable by an authenticated operator who holds the 'Firewall Alias Edit' privilege and can point a GeoIP alias at an attacker-controlled source URL. The GeoIP importer's process_zip() and process_gzip() routines trust the CSV country_code field when building output filenames under /usr/local/share/GeoIP/alias, so a crafted value traverses out of that directory and writes attacker-controlled files as root; chaining a planted newsyslog fragment with an oversized log file then lets the default hourly root cron job execute the payload, yielding complete firewall compromise (CVSS 9.9, AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H). No public exploit code and no confirmed active exploitation were identified at time of analysis, and exploitation requires a non-default alias configuration that the operator must supply.
Local privilege escalation in TotalAV versions up to 7.1.17 allows an authenticated but unprivileged local user to impersonate the SYSTEM service by forging a gRPC IPC authentication token, leading to arbitrary code execution as NT AUTHORITY\SYSTEM. Publicly available exploit code exists (a proof-of-concept C file is linked in the disclosure), though CISA KEV does not list the vulnerability as actively exploited, and the SSVC assessment rates exploitation as 'poc' with total technical impact. Exploitation requires a local foothold and the vulnerable TotalAV service to be running; it cannot be triggered remotely or against hosts without TotalAV.
Path traversal in PeaZip's archive object preview handler allows a crafted archive entry to escape the extraction directory and be handed directly to ShellExecuteW, so a victim who opens a malicious archive on Windows and invokes 'Preview with... -> Associated application' (Shift+Ctrl+O) on the rogue entry can be made to launch an arbitrary program already present on their system without the usual dangerous-extension warning. Affected are PeaZip 11.2.0 and earlier on Windows; no authentication or elevated privileges are needed, but exploitation is interaction-gated (local file delivery plus a deliberate multi-step preview action, CVSS 4.0 base 8.4 with AV:L/UI:A/PR:N and high C/I/A impact). A proof of concept was demonstrated against official vendor builds on two archive formats (.zip and .tar), confirming the defect is in PeaZip's own path handling rather than a single format parser; no CISA KEV entry or independent confirmation of active exploitation was reported at time of analysis. The practical limitation is that the flaw launches programs that already exist at the resolved path (for example a system binary) rather than dropping new attacker-supplied binaries.
Path traversal in QNAP Qsirch lets remote attackers reach the full-text search application without authentication and read files and system data outside the intended directory structure on the host NAS. The vendor states the flaw is fixed in Qsirch 7.0.3.0 and later, so only NAS devices running an earlier build of this optional app - and exposing its web interface to the attacker's network path - remain at risk; no public exploit code and no confirmed active exploitation were identified at time of analysis. Our independent assessment scores the issue at CVSS 3.1 8.6-class severity on the confidentiality axis (C:H/I:N/A:N), meaning the realistic worst case is read-only disclosure of sensitive files rather than the file modification or service disruption implied by the higher input CVSS 4.0 score of 9.3.
Authenticated path traversal in QNAP QuMagie lets an attacker who already holds a QuMagie administrator account read files and system data outside the intended media library on the underlying QNAP NAS. The flaw is remote, network-reachable and low-complexity, but the PR:H privilege requirement in the CVSS vector means it is not exploitable by anonymous users against default installations; no public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV. QNAP has shipped a fix in QuMagie 2.9.1 and later, so exposure is limited to NAS deployments still running older QuMagie builds and reachable by an admin-level account.
Authenticated path traversal in QNAP Video Station before 5.8.8 allows a remote attacker with a valid low-privileged user account to read arbitrary files and system data outside the intended application directory. The flaw is CWE-22 and requires network access with low complexity and no user interaction, but the PR:L vector means an attacker must first hold a Video Station account, limiting mass exploitation. no public exploit identified at time of analysis, and QNAP has released Video Station 5.8.8 as the fix. The vendor CVSS 4.0 score is 8.7, but independent assessment scopes impact to confidentiality only, so it is a genuine moderate-priority issue rather than a top-tier emergency.
Path traversal in QNAP Qsync Central allows an attacker who already holds a valid Qsync Central user account to read files and system data outside the intended directory scope on the NAS. The flaw originates from improper limitation of a pathname to a restricted directory (CWE-22); because the CVSS vector specifies PR:L, exploitation is authenticated - remote unauthenticated Internet attackers cannot reach it against default configurations. Impact is assessed as information disclosure of high confidentiality value rather than code execution or data destruction, and no public exploit code has been identified at time of analysis. All versions prior to Qsync Central 5.0.0.6, 5.1.0.2, and 5.2.0.4 are affected, and QNAP has released fixed builds on each of these branches.
Arbitrary file overwrite in HPE NonStop Python 3.x lets an attacker who supplies a crafted TAR archive escape the intended extraction directory via .. (dot-dot) sequences in member filenames and clobber files on the NonStop host, with the overwritten data potentially leading to code execution or system compromise depending on the privileges of the extracting process. The vendor rates this 8.0 (CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), while our independent assessment scores it lower at CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H, treating it as local rather than adjacent-vector and integrity/availability-only; unauthenticated access is implied by PR:N in both vectors, but successful exploitation is not automatic - it requires the victim to extract an attacker-controlled archive (UI:R), and the write primitive is bounded by the privileges of the extracting account. No public exploit code was identified at time of analysis, there is no CISA KEV entry, and no EPSS score was supplied, so real-world risk is moderated by the mandatory user interaction rather than by the headline score.
Path traversal in QNAP's QcalAgent (Qcalendar) app for NAS devices lets a remote attacker who already holds a low-privileged user account read files and system data outside the intended directory. Only installations running QcalAgent 1.1.x below 1.1.10 are exposed, since the flaw is fixed in 1.1.10 and later, and the authentication prerequisite (PR:L in both the vendor CVSS 4.0 vector and our assessed CVSS 3.1 vector) means unauthenticated outsiders cannot reach it. No KEV listing and no public exploit code exists at time of analysis, but the vendor scores it 8.7 under CVSS 4.0, so patching should be prioritized wherever the optional app is installed and user accounts are shared broadly.
Authenticated path traversal in QNAP Download Station allows a remote user with a valid account to read arbitrary files outside the intended directory, potentially exposing system data. Affected versions are Download Station 5.10.x before 5.10.2.313 and 5.11.x before 5.11.3.322; the vendor has released fixes. No public exploit code or active exploitation has been identified at time of analysis, and the risk is conditional on valid credentials and network reachability to the NAS.
Unauthenticated arbitrary file read in the dbt docs serve component (dbt 2.0.0-alpha.0 through 2.0.0-alpha.4) lets any client that can reach the server POST attacker-chosen SQL to /api/v1/query and invoke DuckDB filesystem-reading functions, returning the contents of files readable by the dbt process - including paths outside the docs index directory. The SQL handler was removed entirely in 2.0.0-alpha.5. Reachability is the gating prerequisite: dbt docs serve binds to localhost by default, so remote exploitation only succeeds when an operator has exposed it via the host option or the DBT_DOCS_HOST environment variable; no public exploit code was identified at time of analysis, and no KEV listing is associated with this issue. The vector is unauthenticated (PR:N) with high confidentiality impact only (VI:N, VA:N), giving a 4.0 base score of 8.2 and an assessed 3.1 score of AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N.
Arbitrary filesystem write in Ludwig versions prior to 0.17.8: the dataset archive extraction routine (ludwig.datasets.archives.extract_archive) validates tar member names but never validates symlink or hard-link members, so a crafted archive can create a link that escapes the extraction directory and then write a later member through that link, placing attacker-controlled content at an arbitrary path with the extracting process's privileges. The same name check relied on os.path.commonprefix, a character-based comparison that also lets a sibling path sharing the destination's character prefix pass. Exploitation requires the victim to load a dataset whose configured archive URL points at an attacker-controlled or attacker-compromised tar file (CVSS 3.1: AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H - unauthenticated from the network, but mandatory user interaction), and is limited to Python 3.12 and 3.13 runtimes because Python 3.14's default tar 'data' filter already rejects escaping links; no public exploit code or confirmed active exploitation was identified at time of analysis.
Path traversal in F´ (F Prime) prior to 4.3.0 lets an authenticated peer on the file-uplink channel write or overwrite files at attacker-chosen writable filesystem locations by supplying a crafted destination path in a Fw::FilePacket::StartPacket. The flaw yields high integrity impact and limited availability impact (overwriting or damaging critical files), with no confidentiality impact, and CVSS reflects PR:L because the attacker must already be able to send file-uplink packets to Svc::FileUplink. The issue requires no non-default feature toggle once uplink access is obtained, and no public exploit code has been identified at time of analysis; vendor-released patch: 4.3.0.
Cloud Commander (cloudcmd) versions 19.20.2 through 19.21.1 expose a path traversal flaw in the GET /api/v1/pack endpoint that lets unauthenticated remote attackers read arbitrary files outside the configured --root directory, with the stolen content returned as a downloadable tar.gz archive. The root cause is a handler that calls the unguarded root() helper at server/rest/index.js:130 instead of the root.resolve() validation wrapper used on other endpoints, so percent-encoded traversal sequences in the pack path escape the intended document root and reach files such as /etc/passwd or SSH private keys. Impact is confidentiality-only (no write or code-execution primitive), and no public exploit identified at time of analysis, though a vendor patch (v19.21.2) and a public technical write-up are available; exploitation requires network reachability to the cloudcmd HTTP service, which many deployments gate behind localhost binding, a reverse proxy, or optional authentication.
Unauthenticated remote attackers can bypass access controls in the TSplus Remote Access web server via manipulated paths on the /socket.io/JWN/ endpoint, leading to disclosure of protected internal resources. This high-severity vulnerability (CVSS 4.0 base 8.7) affects internet-exposed portals with no authentication or user interaction required. No public exploit identified at time of analysis, but the flaw is trivially exploitable given network reachability.
Unauthenticated local file inclusion in the Ultimate Multisite WordPress plugin before 2.17.2 allows remote attackers to traverse the filesystem and read arbitrary local files, including wp-config.php with its database credentials and authentication salts. The plugin passes a user-supplied file-selection value directly into an include operation without validation, and the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N) confirms no authentication and no user interaction are required. Publicly available exploit code exists, but EPSS is low at 0.20% (10th percentile) and CISA SSVC records no known exploitation, so real-world risk is concentrated in internet-reachable WordPress sites that have the plugin active.
A path traversal flaw in Adobe ColdFusion's Remote Development Services (RDS) component allows arbitrary file system read outside the intended directory scope, exposing configuration files, credential stores and source code on servers where RDS is reachable. Affected builds are ColdFusion 2023 up to and including 2023.0.25 and ColdFusion 2025 up to and including 2025.0.13; per the CVSS vector (PR:N/UI:N) no credentials or user interaction are required once RDS is accessible, so the practical gate is deployment mode rather than authentication. Adobe scores this 9.3 Critical (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H), but our reassessment scores it CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N because RDS is network-reachable on exposed servers while the integrity and availability components are not supported by the path-traversal-to-file-read primitive; no public exploit code and no confirmed active exploitation were identified at time of analysis, and real-world exposure is limited to dev, staging or legacy servers that have left RDS enabled (Production Secure Profile disables it automatically).
Authenticated path traversal in Omnispace Agora Project before 26.10.0 lets a low-privileged user write attacker-controlled files outside the intended upload temporary directory by supplying an unanchored tmpFolderName value in the upload destination path; pointing it at the web root can yield remote code execution if the written file is executable from that location. Per the CVSS vector (PR:L), a valid low-privileged account on the Agora web application is required, so exposure is materially lower on instances with restricted account provisioning or closed self-registration, and versions 26.10.0 and later are unaffected. CVSS 8.7 (v4.0) reflects high confidentiality, integrity and availability impact; no public exploit code or confirmed active exploitation was identified at time of analysis, and a vendor patch (26.10.0) is available.
Arbitrary file-system write in Adobe Experience Manager 6.5 (through 6.5.25) and AEM 6.5 LTS (through LTS SP3) allows an authenticated low-privileged attacker to place files in unauthorized locations on the host by sending a crafted request that manipulates a pathname and escapes the intended directory. No user interaction is required and attack complexity is low, but the attacker must already hold a valid low-privilege AEM account and be able to reach the instance over the network; the assessed vector (AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N) shows a scope change with high integrity impact and no direct confidentiality or availability impact. No public exploit code and no confirmed active exploitation were identified at time of analysis, so this is a credentialed post-authentication persistence and integrity risk rather than an opportunistic internet-wide exploit, though it is a credible escalation step for anyone who already has a foothold in AEM.
Remote code execution in Visual Studio Code (versions 1.0.0 up to but not including 1.141.1) is achievable through a path traversal flaw when a victim opens a crafted workspace, folder, or repository containing malicious pathnames that escape the intended restricted directory. The attack is unauthenticated (PR:N) but requires user interaction (UI:R), and the scope change (S:C) alongside high confidentiality, integrity, and availability impacts yields a CVSS score of 9.6. Microsoft has released a vendor patch (1.141.1); no public exploit code has been identified at time of analysis, though the severity warrants prompt patching.
Relative path traversal in OpenSSH for Windows (CWE-23) can allow an unauthenticated remote attacker to escape intended directories during an SSH interaction and, ultimately, execute code on the affected host - carrying a CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) and rated by SSVC as having total technical impact. Exploitation is not attacker-autonomous: it requires the victim to use the OpenSSH for Windows component and to initiate or accept an SSH connection to an attacker-controlled or compromised endpoint (the UI:R user-interaction requirement), and the host must be running a build below its fixed release (for example Windows 11 24H2 below 10.0.26100.9711 or Windows Server 2022 below 10.0.20348.5761). Current intelligence shows no public exploit identified at time of analysis, SSVC exploitation status of 'none', and non-automatable delivery, so this is a high-priority-on-paper issue whose real-world urgency is tempered by the lack of confirmed exploitation - vendor patches are available per the Microsoft advisory and should still be prioritized.
Local privilege escalation in Windows Shell allows an authenticated attacker who already holds low-privileged code execution on a Windows host to elevate to SYSTEM-level rights by supplying a crafted relative path to a privileged shell operation, causing path-traversal sequences to escape the intended directory (CWE-23, CVSS 3.1 7.8, AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Affected are default installations of the Windows client and server builds enumerated in the vendor and EUVD data, spanning Windows 10 1607 through 22H2, Windows 11 23H2 through 26H2, and Windows Server 2012 through 2025, including Server Core variants. There is no public exploit identified at time of analysis and CISA's SSVC decision framework records exploitation as none with automatable set to no, so this is a patch-priority item rather than an emergency; vendor patches are available and no user interaction is required once the attacker has local access.
Privilege elevation in the Windows Encrypting File System (EFS) lets an authenticated remote attacker supply an absolute path that EFS resolves outside its intended directory, yielding high impact across confidentiality, integrity, and availability (CVSS 8.8, CWE-36). Every supported Windows client and server generation is affected - Windows 10 (1607 through 22H2), Windows 11 (23H2 through 26H2), and Windows Server 2012, 2012 R2, 2016, 2019, 2022, and 2025, including Server Core installations - while exploitation requires the attacker to already hold valid low-privilege credentials and network reachability to the EFS service (PR:L, AV:N), with no user interaction needed. No public exploit code and no confirmed active exploitation have been identified at time of analysis per CISA's SSVC (Exploitation: none, Automatable: no), though the assessed technical impact is total; Microsoft has shipped vendor patches.
Path traversal in Skype for Business Server allows an authenticated attacker to elevate privileges over the network by exploiting absolute path traversal (CWE-36). Affected versions include Skype for Business Server 2019 CU8 below build 7.0.2046.583, Subscription Edition CU1 below build 7.0.2046.889, and 2015 CU13 below build 6.0.9319.886. No public exploit identified at time of analysis, and CISA SSVC rates exploitation as 'none' with 'Automatable: no', though the required authentication limits real-world risk.
Path traversal in on-premises Skype for Business Server (including the Microsoft Lync lineage) lets an attacker who already holds a low-privileged authenticated account on the service send a crafted network request containing an absolute file path and achieve code execution, scoring CVSS 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Affected builds are Skype for Business Server Subscription Edition before 7.0.2046.889, Skype for Business Server 2015 CU13 before 6.0.9319.886, and Skype for Business Server 2019 CU8 before 7.0.2046.583; the PR:L prerequisite means this is not a pre-auth remote exploit, so realistic risk concentrates on insiders or attackers who have already obtained a valid credential or foothold. No public exploit code has been identified at time of analysis, CISA SSVC rates exploitation as none and the flaw as non-automatable, and though no EPSS score was supplied, the total technical impact combined with an available vendor patch makes prompt upgrading the priority. This is a credible, actionable priority rather than an inflated-CVSS artifact.
Local privilege escalation in Windows Shell allows an attacker who already holds a low-privileged, authenticated account on a Windows host to traverse relative paths and raise their privileges to a higher integrity level (CVSS 3.1 base 7.8, AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Exploitation is not a remote or initial-access vector - it requires existing local code execution or account access, but needs no user interaction and is low-complexity once that foothold exists. CISA's SSVC assessment records no observed exploitation and no automatable path, and no public exploit has been identified at time of analysis; vendor patches are available, making this a credible but second-tier prioritization compared with actively exploited or remotely reachable issues.
Path traversal in .NET (CWE-22) allows an authenticated local attacker to escape an intended restricted directory and elevate privileges on the host, with the same flaw reaching users through the Visual Studio 2022 17.14 and Visual Studio 2026 18.10 toolchains. Successful exploitation requires a local, already-authenticated foothold (PR:L) plus user interaction (UI:R), meaning a higher-privileged user or process must be induced to act on an attacker-influenced pathname; it is therefore not remotely triggerable, and CISA's SSVC assessment records Exploitation: none, Automatable: no, with total technical impact if it does succeed. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV, so this rates as a moderate-priority local privilege-escalation issue rather than an urgent, widely exploitable threat. Vendor patches are available.
Authenticated path traversal in Microsoft SharePoint Server can be escalated to code execution over the network, allowing an attacker holding a valid low-privileged account to fully compromise the confidentiality, integrity, and availability of the affected deployment. On-premises installations are affected: SharePoint Server Subscription Edition below build 16.0.20326.20190, plus SharePoint Server 2019 and SharePoint Enterprise Server 2016, all of which are reachable over the network with the attacker needing only PR:L credentials and no victim interaction (AV:N/AC:L/PR:L/UI:N). There is no public exploit identified at time of analysis and CISA's SSVC assessment marks the issue as not automatable, so while impact is rated total, the authentication prerequisite and lack of automation keep this an above-average-priority rather than emergency-level issue; Microsoft has published a vendor fix.
Path traversal (CWE-22) in Microsoft Dynamics 365 Business Central lets an authenticated, low-privileged user escape an intended restricted directory through network-reachable functionality, with high confidentiality and integrity impact and a CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The required precondition is a valid low-privilege account, so anonymous exploitation is not indicated, and no user interaction or special configuration is needed once that access exists; the exact vulnerable feature or endpoint is not identified in the available description. At time of analysis there is no CISA KEV entry and no public exploit code identified, and no EPSS score was supplied, so this should be treated as a high-severity, patch-now issue driven by its privilege-escalation potential rather than by observed exploitation.
Path traversal in Microsoft Dynamics Business Central (CWE-22) allows an authenticated user holding only low-level privileges to escape an intended directory boundary and elevate privileges over the network, carrying a CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) with high confidentiality, integrity and availability impact and no user interaction required. Because the vector requires PR:L, anonymous remote attackers cannot exploit this alone - the realistic threat is insiders or holders of compromised low-privilege accounts who already possess valid credentials plus network reach to the Business Central application endpoint. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the sole supplied reference is Microsoft's MSRC update guide, which is the authoritative source for fix details.
Path traversal in Fortinet FortiSIEM 7.5.0 can let a remote unauthenticated attacker execute unauthorized code or commands by sending specially crafted packets to the affected service. The CVSS vector shows network exploitation with low complexity, no privileges, and no user interaction, producing high confidentiality, integrity, and availability impact. No public exploit code or confirmed active exploitation was identified in the provided intelligence; consult Fortinet advisory FG-IR-26-180 for the authoritative affected-version and remediation details.
Unauthenticated remote attackers can write arbitrary files on servers running Risesoft-y9 Digital-Infrastructure 9.6.5 through 9.6.11 by abusing a path traversal flaw in the fileManager module's storeFile endpoint; a single crafted POST to /rest/storeFile with attacker-controlled fullPath and fileName parameters lets the service account create or overwrite files anywhere it has write permission, which can escalate to code execution if a writable path is later executed or parsed. The assessed vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H (8.8, matching the published CVSS 4.0 score), reflecting high integrity and availability impact with no confidentiality impact, and no KEV listing, so there is no confirmed active exploitation (no public exploit identified at time of analysis), though the presence of a public technical writeup and a VulnCheck advisory makes weaponization plausible. Real-world impact is bounded by the service account's write permissions and by whether the vulnerable fileManager endpoint is reachable from the attacker's network position rather than internal-only; this is a credible high-priority issue rather than a high-CVSS-but-low-risk paper cut.
Unauthenticated path traversal in Risesoft Digital-Infrastructure 9.6.5 through 9.6.11 lets any network-reachable attacker read arbitrary files from the server by placing parent-directory ('../') segments in the fullPath and fileName parameters of the fileManager /rest/retrieveFileStream endpoint, which is unauthenticated by design and backed by the Y9FileController.retrieveFileStream handler. Because the traversable location includes application configuration such as application.yml, successful exploitation exposes database, Redis and Nacos credentials - high confidentiality impact with no write or code-execution component. Both the vendor-source reference and the assessed CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N vector (7.5) confirm no authentication or user interaction is required; no public exploit identified at time of analysis, though a public technical write-up describing the traversal is referenced by VulnCheck.
Ivanti Xtraction versions prior to 2026.4 are vulnerable to a path traversal flaw in the template export feature, allowing an authenticated attacker with low privileges to read arbitrary files accessible to the service account. Exploitation requires a valid session but no user interaction, and while confidentiality is compromised, no public exploit code or active exploitation has been identified; this is a genuine but second-tier priority rather than an emergency.
Path traversal in Commvault HyperScale MediaAgents allows an authenticated low-privileged user to read files outside the intended directory over the network, resulting in unauthorized disclosure of data (rated 7.1, confidentiality-only impact with no integrity or availability effect). The flaw requires a valid session to the MediaAgent service (PR:L per the assessed vector), so anonymous internet attackers cannot trigger it - stolen, shared, or insider credentials are the realistic precondition. No public exploit code and no confirmed active exploitation were identified at time of analysis, and Commvault reports that software customers should upgrade to the resolved maintenance release; exact affected versions and deployment modes should be confirmed against advisory CV_2026_10_8.
Path traversal in the Wazuh Manager cluster upload handlers (upload_list_file, upload_rule_file, upload_decoder_file) lets an attacker who holds the cluster authentication key write files to arbitrary paths on the manager as the wazuh user, with '../' sequences in the filename parameter slipping past REST controller validation. Affected versions are Wazuh 4.1.1 through 4.14.7 (fixed in 4.14.8); exploitation requires the manager to be running in cluster mode and the actor to already possess the shared cluster key, so this is a post-compromise/lateral-movement primitive against clustered deployments rather than an internet-facing unauthenticated bug. No public exploit code has been identified at time of analysis and the flaw is not confirmed actively exploited (not in CISA KEV), but the integrity and availability impact is high once the key prerequisite is met, and the vendor has shipped a patch.
Path traversal in Wazuh Manager 4.1.1 through 4.14.7 lets an attacker who has already compromised a cluster worker node read or delete arbitrary files on the cluster master - including rbac.db - by sending traversal or absolute-path filenames through the internal cluster RPC channel. The flaw is a post-compromise, lateral-escalation primitive: it requires a multi-node deployment, adjacent network position inside the cluster, and high worker-level privileges (PR:H), and it bypasses the REST API's filename validation and RBAC enforcement because the equivalent REST endpoints do validate paths. No public exploit code or confirmed active exploitation was identified at time of analysis, and the vendor has released a patch in Wazuh 4.14.8.
Path traversal in Wazuh Manager's delete_rule_file and delete_decoder_file helpers lets an attacker who holds the Wazuh cluster key delete arbitrary files as the wazuh user, including ossec.conf, client.keys, and rule files. Affected versions are 4.1.1 through 4.14.7 (fixed in 4.14.8), tracked by CPE cpe:2.3:a:wazuh:wazuh-manager. Exploitation is not unauthenticated: the CVSS 4.0 vector carries PR:H and the assessed 3.1 vector is AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H, meaning the attacker must already possess the cluster key and be able to invoke the DistributedAPI helpers as a cluster worker, so practical exposure is limited to clustered multi-node Manager deployments where the key has leaked or a worker node is compromised; no public exploit code was identified at time of analysis and there is no confirmed active exploitation (CISA KEV).
Path traversal in NLTK's WekaClassifier integration (all versions through 3.10.3) lets attackers who control the model_filename or model argument escape nltk.pathsec containment and drive the Weka JVM to write files outside permitted data roots via the -d option, or probe for file existence via -l. There is no public exploit identified at time of analysis and the flaw is not confirmed actively exploited (CISA KEV), but exploitation requires an application that wires attacker-controllable values into WekaClassifier and has a working Weka Java/JVM toolchain installed - a non-default, niche integration that most NLTK deployments never invoke. Under those preconditions, the CVSS 4.0 base score of 8.3 is driven by a network vector with high integrity impact (VI:H), while the AT:P metric reflects the required application-wiring precondition.
Path traversal in the NVIDIA AIStore for Linux dSort archive extraction component allows a remote attacker to write files outside the intended extraction directory by submitting a dSort job that references an archive (e.g., tar/zip) whose member names contain crafted traversal sequences, yielding arbitrary file creation or overwrite and potentially code execution, information disclosure, data tampering, and denial of service. The vulnerability carries a CVSS 3.1 base score of 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) per the assessed vector, indicating remote reachability and no authentication requirement, but a high attack-complexity rating that reflects the difficulty of reliably crafting the malicious archive and triggering the flaw. There is no confirmed active exploitation (CISA KEV) and no public exploit code identified at time of analysis; the practical gating factor is network access to the AIStore dSort/API endpoint, which in typical deployments is confined to a trusted ML/training cluster or private network rather than being internet-facing. Because the dSort job-submission path is the attack surface, exposure is primarily amplified where AIStore's API is reachable from untrusted networks, and no user interaction is required.
Unauthenticated path traversal in the NVIDIA AIStore Promote API on Linux lets a remote attacker read arbitrary files that the AIStore process can access by supplying a crafted absolute source path, resulting in high-confidentiality information disclosure (CVSS 3.1 base 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N). Any network-reachable deployment where the Promote endpoint is enabled and functional is at risk, since the vector requires no authentication (PR:N) and no user interaction (UI:N). No public exploit code and no confirmed active exploitation were identified at time of analysis; the practical blast radius is bounded by the OS privileges of the AIStore process account and by whether the Promote API is exposed beyond trusted internal networks, making this a genuine but moderate-priority issue rather than a critical emergency.
Unauthenticated path traversal in the target-side object rename handler of NVIDIA AIStore on Linux allows a remote attacker who can reach a target (storage) node directly to write files outside the intended storage directory by supplying a crafted rename destination, resulting in arbitrary file creation or overwrite. NVIDIA rates the issue CVSS 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, CWE-22), with downstream consequences that could include code execution, privilege escalation, information disclosure, data tampering, and denial of service depending on what the overwritten path controls. Exploitation is constrained rather than trivial: the attacker needs network reachability to a target node - not merely the front-end proxy - and must build a traversal payload the rename handler accepts, so exposure is greatest in flat cluster networks or environments where target ports are directly reachable; no public exploit code and no CISA KEV entry were identified at time of analysis.
Path traversal in the Siemens .NET Client Library for the SIMATIC S7 Webserver API (all versions prior to V3.3.61) lets a remote attacker who controls or man-in-the-middles the server that the client downloads tickets from specify a crafted filename and thereby write arbitrary files outside the intended download directory. Integrity impact is high (VI:H) while confidentiality and availability impacts are none, consistent with the vendor's CVSS 4.0 base score of 8.7; the CVSS vector indicates no privileges (PR:N) or user interaction (UI:N) are required, so the only real prerequisite is that the attacker already occupies the server/MITM position relative to the victim client. The additional ability to replace existing files is limited to deployments where file overwriting is enabled. No public exploit code was identified at time of analysis and there is no indication of confirmed active exploitation.
Directory traversal in the iKuai8 management interface shipped on the IK-Q3000 Enterprise-grade Wi-Fi 6 router lets an attacker escape the intended file path and execute arbitrary code on the device; affected builds are Enterprise Edition <= iKuai8_3.7.23_Enterprise Build 202606021825 and Free Edition <= iKuai 8_4.0.304-beta. The CVE record scores this 9.8 with a PR:N vector (unauthenticated), but the public disclosure is explicitly titled 'authorized' path traversal and our independent assessment rates it PR:L, so a valid authenticated management session is most likely a prerequisite and is the key factor limiting real-world exploitation. There is no CISA KEV entry and no public exploit identified at time of analysis, and EPSS is low at 0.45% (38th percentile); exposure is further gated by network reachability to the router's administrative web service, so units with management bound to an internal/LAN interface are materially less exposed.
Authenticated remote code execution in IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 arises from improper validation of file paths inside archives the platform extracts, allowing an attacker with a valid account to write files to arbitrary locations and execute code under the privileges of the TRIRIGA service (CVSS 3.1: 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The attack is network-reachable with no user interaction and low complexity, but the PR:L vector gates it behind an existing authenticated session, confining realistic exploitation to insiders or attackers who have already obtained platform credentials. No public exploit identified at time of analysis, and IBM has published a vendor patch advisory covering the affected 5.0.0-5.0.8 range.
Arbitrary file write via path traversal in IBM Planning Analytics 2.0 and 2.1 allows remote unauthenticated attackers to write files to arbitrary locations on the server by submitting a crafted URL containing '/../' sequences. The vulnerability carries a CVSS 3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N), indicating high integrity impact but no confidentiality or availability impact. A vendor patch is available per IBM support node 7291604, and no public exploit identified at time of analysis.
Path traversal in IBM Planning Analytics 2.0 and 2.1 allows a remote attacker to read arbitrary files from the host and overwrite certain application files by supplying crafted file paths to the service. The CVSS 3.1 vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N, base 8.2) confirms network reachability, low attack complexity, no authentication requirement (PR:N), and no user interaction, with high confidentiality impact and limited integrity impact. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis; the vendor has released a fix referenced in the IBM advisory.
Denial of service in IBM DataStage on Cloud Pak for Data 5.4.0.0 can be triggered by a remote user who already holds valid platform credentials and supplies path traversal sequences to the product's file-handling logic, disrupting or halting the service. Exploitation requires an authenticated session with low privileges (CVSS vector PR:L) and no action by a victim, so the practical barrier is credential access rather than network reachability; availability is the realistic impact, with no evidence of code execution. A vendor patch is available via IBM support advisory node 7288649, and no public exploit code or confirmed active exploitation was identified at time of analysis.
Authenticated path traversal in IBM DataStage on Cloud Pak for Data 5.4.0.0 allows a remote attacker holding a valid platform account to bypass intended directory restrictions and execute arbitrary code. Exploitation requires only low-privileged credentials (CVSS PR:L), needs no user interaction, and is network-reachable with low complexity, which is why the vector scores 9.9 Critical with a scope change (S:C) reflecting impact that can extend beyond the vulnerable component. Despite the high score, the practical risk picture is more moderate: EPSS is only 0.49% (40th percentile), CISA SSVC rates exploitation as none with automatable set to no, there is no public exploit code identified at time of analysis and no KEV listing, and the vendor has published a patch, so remediation is available rather than dependent on compensating controls alone.
Path traversal in IBM Maximo Application Suite 8.10, 8.11, 9.0, 9.1 and 9.2 lets remote, unauthenticated attackers read arbitrary files from the server by sending crafted URL requests containing '../' sequences. The flaw carries a CVSS 3.1 score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), so impact is confined to confidentiality with no data modification or denial of service, and the independent assessment rates the overall signal as moderate and internally consistent rather than alarming. No public exploit code was identified at time of analysis and the CVE is not listed in CISA KEV; practical exposure depends mainly on internet reachability and on the OS-level file permissions of the account running the Maximo web process, since only files that account can read are disclosed.
Path traversal in ConvertX (all releases prior to 0.18.0) lets an authenticated user write converted output files to arbitrary paths inside the container by supplying traversal sequences in the convert_to parameter of the /convert endpoint. The CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H reflects that exploitation requires a valid account by default, though instances deliberately configured for unauthenticated access lower that bar to anyone who can reach the service; the payoff is integrity and availability impact - overwriting files or causing denial of service - rather than data disclosure. A vendor fix is available in 0.18.0 (upstream PR 532, commit 0965928), and no public exploit code or confirmed active exploitation was identified at time of analysis, keeping this a credible above-average-priority issue rather than a top-tier emergency.
Authenticated users of the MarkLogic Query Console can read arbitrary files from the underlying server by supplying unsafe path values to a privileged filesystem helper, a classic path-traversal disclosure (CWE-22). The issue affects MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7, and carries a CVSS 3.1 base score of 7.7 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N), meaning a network-reachable, low-complexity attack by an authenticated principal that yields high confidentiality impact with no integrity or availability effect and a scope change because the helper runs with privileges beyond the caller's own. Because exploitation requires valid Query Console credentials, this is a credible moderate-to-high priority patching item rather than a drop-everything emergency; no public exploit code or confirmed active exploitation was identified at time of analysis.
Path traversal in the legacy InfoStudio modules shipped with Progress MarkLogic Server lets a low-privileged authenticated remote attacker reach files outside the intended module directory and, because user-context values are also insufficiently validated, potentially have code run under an unintended identity. Affected deployments are MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7 that still have the legacy InfoStudio modules present and reachable. The vendor rates this 8.5 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N), reflecting a confidentiality-first impact that crosses a security boundary; no public exploit code has been identified at time of analysis and the flaw is not confirmed as actively exploited, but fixed builds are already available, so this is a priority patching item rather than an emergency.
A path traversal flaw in rebar3, the standard build and dependency-management tool for Erlang/OTP, lets a malicious Hex package publisher cause rebar3 to delete an arbitrary directory and write package files into it whenever a developer or CI job fetches that package's dependencies. The attack abuses an unvalidated 'app' field in Hex registry dependency metadata: rebar3 treats that field as the dependency directory name, so a value such as '../../../../target' resolves outside the project's _build tree and is then removed with rm -rf before the fetched package is moved into place. Only rebar3 3.7.0-rc1 through 3.27.1 is affected, exploitation requires user interaction (a developer running rebar3 get-deps against a project that pulls in the malicious release, directly or transitively), and because the deletion occurs before the dependency's rebar.config.script is evaluated and get-deps compiles nothing, the practical impact is destructive file deletion and overwrite rather than immediate code execution; no public exploit code has been identified at time of analysis, and the public hex.pm registry added validation for the field on 2026-10-12, leaving private or self-hosted Hex registries as the main residual exposure.
Path traversal in the Hex package manager for the Elixir/Erlang (Mix) ecosystem, versions 0.6.0 through 2.5.1, lets a malicious package publisher delete a directory outside the project's deps/ folder and write the package's files into that location when a developer runs mix deps.get or mix deps.update. The attacker abuses a dependency's OTP application label, which Hex copies from the signed registry without validation and Mix joins onto deps/ as the checkout path, so a crafted label such as '../../target' escapes the project tree through File.rm_rf!/1 before any dependency code is compiled. Exploitation requires the victim project to depend directly or transitively on the attacker-controlled release and the developer to explicitly fetch dependencies, so no victim-side authentication is needed (PR:N) but user interaction is required; no public exploit identified at time of analysis, and the vendor rates it CVSS 7.5.
Authenticated back-office users of Thelia through 2.6.1 can chain a path traversal flaw in the translation editor with a PHP string-escaping failure to write and execute arbitrary PHP code on the server, achieving remote code execution with web-server privileges. The attack requires a back-office account holding UPDATE-level permission on the admin.configuration.language resource (CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, assessed 8.8), so it is not reachable by unauthenticated or low-privilege users despite the network attack vector; no public exploit code and no confirmed active exploitation were identified at time of analysis, and EPSS is low at 0.47% (39th percentile), making this a high-impact but moderate real-world priority.
Arbitrary file write in Progress ShareFile Storage Zones Controller 5.12.6 and earlier lets an unauthenticated remote attacker who can influence the remote file identifier consumed by FileCopyService place attacker-controlled content into any filesystem location writable by the Storage Zones service account. Escalating that write to remote code execution requires a second, non-default condition: an IIS-served directory that is both executable and writable by that same account, which is why the assessed attack complexity is high. No public exploit code has been identified at time of analysis, and the risk profile is configuration-dependent rather than a mass-exploitation emergency.
Path traversal in the OTRS SendSupportBundle functionality allows an authenticated administrator to delete files outside the intended directory, limited by the operating system permissions of the OTRS application process. The issue affects OTRS versions 7.0.X through 2026.X before 2026.7.X, as well as ((OTRS)) Community Edition 6.x and earlier; products based on Community Edition are likely affected. Despite a high CVSS score of 8.7, exploitation requires a valid administrative account and does not bypass OS file permissions, and no public exploit has been identified.
Persistent code execution on a penetration tester's workstation is achievable through a relative path traversal (CWE-22) in the Metasploit Framework post module post/apple_ios/gather/ios_image_gather, affecting versions prior to 6.5.5. A hostile or tampered iOS device can return a crafted directory-listing entry (for example ../../msfconsole.rc) that the module interpolates without sanitization into the local destination path handed to client.fs.file.download_file(), overwriting ~/.msf4/msfconsole.rc, which every msfconsole invocation automatically executes at startup; because the written resource file can load a second written Ruby plugin, this converts into an interactive shell as the operator (frequently root) at the next console launch. Exploitation is not remote-unauthenticated against a default service: it requires operator interaction (UI:R) to run the specific gather module against an attacker-controlled Meterpreter session, no workstation authentication (PR:N) is needed, and the assessed attack complexity is High because the hostile device, the specific module, and the resulting file write must all align; no public exploit code was identified at time of analysis, and the flaw is fixed in the 6.5.5 release.
Authenticated users of Blinko through version 1.8.8 can achieve remote code execution as root by supplying a plugin name containing '../' sequences to the plugin.installPlugin tRPC procedure, which constructs the install path from the unsanitized name and writes downloaded plugin files outside the plugins directory. Because the official Docker image runs as root, an attacker can overwrite a root-owned startup file and gain code execution at the highest privilege level; the endpoint is open to any authenticated account and the referenced sign-in code indicates self-registration may be enabled, potentially letting an unauthenticated outsider obtain the required account. The assessed vector is CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (8.8), reflecting a genuine high-priority issue rather than a CVSS-inflated paper risk; no confirmed active exploitation is indicated by CISA KEV, though the references include a public repository dedicated to this path-traversal RCE chain that should be treated as potential exploit material.
Authenticated members of pH7Builder (pH7 Social Dating CMS) instances running versions before 18.5.0 can delete arbitrary files on the host by submitting ../ traversal sequences in the POST picture_link parameter handled by the picture module's deletePhoto() action. Because the parameter is concatenated unsanitized into the public picture storage directory, an attacker can escape that directory to remove other members' photos as well as application configuration and cache files, producing content loss and a denial-of-service condition (CVSS 3.1 base 7.1, AV:N/AC:L/PR:L/UI:N, C:N/I:H/A:H; vendor/SI scoring 7.2 under CVSS 4.0). Impact is limited to destructive deletion - there is no file read/exfiltration and no code execution path - and no public exploit code was identified at time of analysis, with no CISA KEV listing.
Arbitrary file deletion in the ChimpStudio FoodBakery WordPress theme (versions up to and including 4.6) allows an authenticated attacker holding only a Subscriber-level account to delete arbitrary files on the server, with no user interaction required. The underlying path traversal flaw (CWE-22) lets a crafted request escape the intended directory and reach sensitive files such as wp-config.php, so the scope change (S:C) escalates impact beyond availability loss toward full site compromise. Rated CVSS 7.7 (AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H); no public exploit identified at time of analysis, and exploitation is gated by whether the site permits attackers to hold a Subscriber account, which is trivial on sites with open self-registration and meaningfully harder where registration is disabled or restricted.
Authenticated subscribers can delete arbitrary files on WordPress sites running PeepSo versions up to 9.0.5.4 due to a path traversal flaw (CWE-22). This high-severity (CVSS 7.7) vulnerability requires only a low-privilege account, which is easily obtained on sites with open registration, and allows deletion of critical files, potentially leading to site compromise or denial of service. No public exploit code has been identified at time of analysis.
Attackers can delete arbitrary files outside the intended directory in rtMedia for WordPress, BuddyPress and bbPress (buddypress-media) versions up to 4.7.13 due to a path traversal flaw, causing high integrity and availability impact. The published CVSS score is 9.8, but our assessment indicates a likely authenticated vector (PR:L) and no confidentiality impact; authentication requirements are not confirmed from available data. No public exploit code or active exploitation has been identified at time of analysis.
Unauthenticated arbitrary file read affects the Divi Plus plugin for WordPress through version 2.4.0, letting any remote attacker retrieve files from the web server via the svg_image parameter of the /wp-json/elicus/v1/dipl-modules/svg-animator REST endpoint. The endpoint's permission callback returns true unconditionally and the input checks used (sanitize_text_field() and esc_html()) do not block filesystem paths, the file:// stream wrapper, or arbitrary URLs, so the raw contents of the targeted file are returned in the JSON 'html' field; the issue is rated CVSS 3.1 7.5 HIGH (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N). No public exploit code has been identified at time of analysis, and no EPSS score or CISA KEV listing was provided, but successful reads of sensitive files such as wp-config.php could enable follow-on remote code execution.
Unauthenticated remote attackers can delete arbitrary files on WordPress/WooCommerce sites running the PPOM - Product Addons & Custom Fields for WooCommerce plugin through version 34.0.10, abusing insufficient path validation in the rename_files function that is reachable via the plugin's cart/order file-handling path. Removing critical files such as wp-config.php can push the site into a re-installation state that is readily leveraged for remote code execution, and because the relocated file is moved byte-identically into the web-accessible wp-content/uploads/ppom_files/confirmed/ directory, the same flaw also exposes arbitrary file read for anything the web server user can read. Wordfence rates it 9.1 and independent assessment confirms CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, i.e. no authentication, privileges, or user interaction required against default internet-exposed configurations; no public exploit code has been identified at time of analysis. This is a genuine high-priority issue, not a CVSS-inflated one, with the main precondition being simply that the vulnerable plugin version is installed, active, and serving requests.
Path traversal in plugNmeet Server through 2.5.2 allows any authenticated meeting participant to read arbitrary files from the host by supplying crafted ../ sequences in the filePath value passed to the whiteboard document-conversion endpoint; the resulting page images are then retrievable without authentication via /download/uploadedFile/. The assessed impact is confidentiality-only (high file read, no write or availability effect) against the server process's readable files, and publicly available exploit code exists - though there is no CISA KEV listing, so this is best treated as a moderate-priority information-disclosure issue rather than a critical emergency. Risk is highest where the plugNmeet process can read secrets, configuration files, or credentials on the same host.
Path traversal in KodExplorer before 4.55 lets an authenticated low-privileged user bypass the archive-extraction sanitizer and write files anywhere on the server by uploading a ZIP archive containing crafted names such as '....//'. Because the overwritten files can include core JavaScript assets, the flaw chains into stored XSS that can lead to administrator account takeover and, ultimately, remote code execution through unrestricted PHP file upload. Exploitation requires a valid low-privileged account and use of the unzip functionality, so this is a credible, actionable priority rather than a drop-everything emergency; no public exploit code has been identified at time of analysis and no CISA KEV entry confirms active exploitation, while a vendor patch is available in release 4.55.
Path traversal in Apache Camel Karavan 3.18.0 through 4.22.0 allows an authenticated user of any role to write arbitrary files outside the project directory by supplying a project file name containing '../' sequences, leading to overwrite of application configuration or classpath files and potential remote code execution in the Karavan container. The flaw is present in default behavior and requires only a valid account (CVSS 8.8, PR:L). No public exploit code or active exploitation has been identified at time of analysis, but the high impact and low privilege requirement make this a genuine high-priority issue.
Unauthenticated remote attackers can read arbitrary files from the underlying web server by exploiting a path traversal flaw in the WordPress plugin PDF for Contact Form 7 (slug pdf-for-contact-form-7) affecting all versions through 7.1.0. Supplying crafted directory-traversal input to the plugin's PDF file-handling/download path lets an attacker escape the intended directory and retrieve files readable by the web server account, a high confidentiality impact with no integrity or availability effect (CVSS 3.1 base 7.5, AV:N/AC:L/PR:N/UI:N). No public exploit code, CISA KEV listing, or EPSS score was identified in the supplied intelligence, so exploitation has not been confirmed as active and the practical attack surface depends on the plugin being installed and activated; note that WordPress core does not ship this plugin, so exposure is limited to sites running it.
Unauthenticated path traversal in ZealousWeb's Generate PDF using Contact Form 7 WordPress plugin, affecting all releases through 4.2.1, lets a remote attacker read arbitrary files from the web server, an impact mirrored by the CVSS 3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N, C:H/I:N/A:N - confidentiality only, no integrity or availability impact). Any WordPress site with this add-on installed, active, and reachable is exposed if its PDF generation/download endpoint accepts unauthenticated requests; the practical limiting factor is the plugin's comparatively small install base rather than any authentication or configuration barrier. At time of analysis no public exploit code has been identified and there is no CISA KEV listing, but the low-complexity, unauthenticated nature of the flaw makes it a natural candidate for automated mass scanning.
Unauthenticated path traversal in gvproxy, the network forwarder shipped in the gvisor-tap-vsock package (used by Podman Desktop, Red Hat OpenShift/CRC tooling and related Red Hat products), lets an attacker who can reach the /services/forwarder/expose control endpoint supply an arbitrary socket path that is passed unsanitised to os.Remove, resulting in deletion of arbitrary files on the host. The defect is reachable without credentials (PR:N) but requires adjacent/guest-side network access to the forwarder API (AV:A), which is normally bound to the virtual network rather than exposed as a routed internet service; impact is limited to integrity and availability (no data disclosure). No public exploit code has been identified at time of analysis and the flaw is not listed as confirmed actively exploited (CISA KEV); an upstream fix exists in gvisor-tap-vsock PR #718. The vendor score of 9.3 (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H) reflects low-complexity, unauthenticated access combined with a scope change and High integrity/availability impact, and the actual risk depends heavily on whether the forwarder control API is reachable by an untrusted guest or adjacent host.
Banks, a Python library for generating LLM prompts from a simple template language, ships a DirectoryPromptRegistry that prior to version 2.5.1 fails to reject symbolic links for its index.json file and for discovered or existing .jinja prompt files. An attacker who can influence the contents of the registry directory - for example by planting a symlink or by controlling files extracted from an untrusted archive into that directory - can cause _scan() and get() to follow a link outside the registry root and disclose arbitrary files, while set(), _save() and _load() can read or overwrite an external link target, giving high confidentiality and integrity impact with limited availability impact. Exploitation requires local placement influence over the prompt directory and applies only to deployments that use DirectoryPromptRegistry and expose that directory to untrusted input, which is why the vendor CVSS 4.0 base score is 7.3 (AV:L/AC:L/AT:P/PR:L/UI:N) and the assessed CVSS 3.1 vector is AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L; no public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis. The issue is fixed in version 2.5.1.
Unauthenticated path traversal in IBM Guardium Data Protection 12.0, 12.1, and 12.2 can be leveraged by remote attackers to execute arbitrary code on the affected deployment, producing a vendor CVSS 3.1 base score of 9.8 from the vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Per that vector the flaw requires no authentication, no user interaction, and no non-default configuration, so the only practical barrier is network reachability of the exposed Guardium interface; because the product is normally deployed inside segmented enterprise networks, internet-wide exposure is expected to be limited. There is no public exploit identified at time of analysis and no confirmed active exploitation, but the worst-case skill and access profile place this in the urgent patching tier for any instance reachable from untrusted networks; the specific traversal entry point and the path from traversal to code execution are not detailed in the available advisory data and should be confirmed against IBM support node 7291674.
IBM Guardium Data Protection 12.1 and 12.2.2 contain a path traversal flaw (CWE-22) that lets a remote, unauthenticated attacker delete arbitrary files on the appliance by supplying traversal-laden input to an affected file-handling function, giving a high-integrity and availability impact with no confidentiality exposure (CVSS 3.1: 9.1, AV:N/AC:L/PR:N/UI:N/C:N/I:H/A:H). No public exploit code has been identified at time of analysis, EPSS is low at 0.36% (28th percentile), and CISA's SSVC decision framework rates exploitation as 'none' with a total technical impact, so this reads as a serious but not emergency-priority issue. Practical risk is bounded by reachability: Guardium is a management-plane appliance normally confined to privileged database and security administrators behind the enterprise perimeter, which narrows the realistic attacker population despite the network-vector rating.
Path traversal in the web management interface of Tektronix 3 Series MDO oscilloscopes running firmware before 1.21.1 lets remote attackers read arbitrary files accessible to the web application by supplying insufficiently validated file paths. The flaw is rated CVSS 3.1 7.5 (AV:N/AC:L/PR:N/UI:N, C:H/I:N/A:N), but unauthenticated exploitation depends on device configuration - deployments that require login to the web interface reduce the practical risk to authenticated users. Impact is limited to confidentiality (file reads, no write or code execution); no public exploit code or confirmed active exploitation was identified at time of analysis, and exposure is bounded by these instruments typically residing on isolated lab networks rather than the internet.
Path traversal in the SCPI FILESystem command interface of Tektronix 3 Series MDO oscilloscopes running firmware before 1.21.1 allows authenticated remote attackers to read or modify arbitrary files on the device. The vulnerability arises from insufficient validation of file paths supplied to filesystem access commands and is rated CVSS 8.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N). No public exploit code or confirmed active exploitation (CISA KEV) has been identified at time of analysis, and exposure is typically limited because the SCPI interface is usually confined to lab or test networks rather than the public internet.
Unauthenticated path traversal in Countly Server before 24.05.50 and 25.03.44 lets remote attackers read arbitrary files that are readable by the server process, by abusing wildcard routes that serve public images and screenshots. The flaw affects deployments configured with the local filesystem backend of countlyFs (api/utils/countlyFs.js) - installs using the GridFS/database backend cannot be reached through these routes - and carries a CVSS 3.1 score of 7.5 (AV:N/AC:L/PR:N/UI:N/C:H/I:N/A:N), so no credentials, privileges, or user interaction are required. Impact is limited to file disclosure (no integrity or availability effect); vendor-released patches exist in 24.05.50 and 25.03.44, and no public exploit identified at time of analysis.
Arbitrary file and directory deletion in Countly Server (versions prior to 24.05.50 and 25.03.44) allows an authenticated user holding data-migration permission to pass a crafted exportid to the migration-deletion route and recursively remove any file or directory tree writable by the Countly server process, resulting in data loss and service disruption. The root issue is a path-traversal flaw (CWE-22) in plugins/data_migration/api/api.js in which the user-controlled exportid reaches clean_up_data in data_migration_helper.js without the sanitizeFilename-based containment checks introduced by the fix. The assessed CVSS 3.1 vector is AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H (base 8.1), confirming a network-reachable, low-complexity attack requiring an authenticated account (PR:L) with no user interaction, with high integrity and availability impact but no confidentiality exposure; no public exploit code was identified at time of analysis and there is no confirmed active exploitation (not in CISA KEV). Vendor fixes are available in 24.05.50 and 25.03.44.
Authenticated path traversal in Thermo Fisher Torrent Suite Software lets a user who already holds a valid low-privilege session on the Torrent Server web interface read arbitrary files that are accessible to the web service account. Per the assessed CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N), impact is confidentiality-only - no write, integrity, or code-execution effect - and the readable scope is bounded by the filesystem permissions of the web service account, so it cannot reach files that account cannot access. No public exploit code or confirmed active exploitation was identified at time of analysis, and the authentication prerequisite confines realistic risk to insiders or attackers who have already obtained credentials; this is a moderate-priority information-disclosure issue rather than a critical emergency. CISA published an ICS medical advisory (ICSMA-26-288-01) covering this flaw.
Unauthenticated path traversal in the 10Web Booster WordPress plugin (versions up to and including 2.34.5) lets remote attackers create arbitrary directories outside the plugin's cache root, with 0777 permissions applied recursively, and plant a cached page inside them by feeding unsanitized GET parameter names and values into the cache path. The write primitive is strictly limited - the filename is hard-coded to source.html and the body is the server-rendered page buffer rather than attacker-supplied content, so no executable file can be planted and code execution is not achievable, with the realistic outcomes being cache poisoning and stray directory creation (published CVSS 7.5 with I:H; the independent assessment revises integrity impact to Low), and no public exploit identified at time of analysis.
Arbitrary file deletion in the Groundhogg CRM, Newsletters and Marketing Automation plugin for WordPress (all versions up to and including 4.9.3) lets an authenticated user who holds the plugin's import_contacts capability - granted by default to Groundhogg's custom Sales Representative role - name an arbitrary server-side path and have the plugin delete it, with a realistic escalation to remote code execution (for example by removing wp-config.php). The flaw is reachable through the contact-import (CSV), REST API, and webhook paths that call copy_file, and it received a CVSS of 8.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H); there is no CISA KEV listing and no public exploit code identified at time of analysis. The practical risk is bounded by the authentication requirement and by the attacker's need to know or guess the absolute path of a valuable target, but the capability is assigned by default and no user interaction or non-default configuration is needed, making this a credible, actionable priority rather than an inflated high-CVSS issue.
Path traversal in WildFly's management take-snapshot operation lets an authenticated user holding only the Monitor RBAC role write a copy of the server configuration to an arbitrary filesystem location and then read it back, bypassing RBAC restrictions to disclose sensitive credentials. This is a credible, moderate-priority privilege-boundary bypass rather than a critical internet-facing threat, because exploitation requires an authenticated management session and a reachable management endpoint; no public exploit code has been identified at time of analysis and no vendor-released patch version is specified in the provided data.
Authenticated remote code execution is possible in Microsoft SharePoint Server Subscription Edition due to a path traversal flaw (CWE-22) that permits an attacker with low-privilege credentials to escape restricted directories and execute code over the network. The vulnerability carries a CVSS score of 8.8 (AV:N/AC:L/PR:L/UI:N) and requires a valid SharePoint session, making it a credible priority for patching but not an immediate emergency according to current evidence. A vendor patch is available, and no public exploit code has been identified at time of analysis.
Unauthenticated path-traversal file writes in the EnergizeLab Eilik and EilikO AI skill upload endpoint allow any remote attacker who can reach the FastAPI AI inference and profiling service to write arbitrary files on the robot's host system by supplying crafted traversal filenames in an upload request. Because the endpoint enforces neither authentication nor path constraints, exploitation is a straightforward, low-complexity primitive that lets an attacker tamper with the AI skill files the robots execute, degrading or subverting robot behavior and causing high integrity and availability impact (CVSS 3.1 base 9.1, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H, CWE-434); confidentiality is assessed as unaffected. The practical limiting factor is network reachability rather than credentials or configuration - these are consumer robots whose service is normally confined to the local network segment, so real-world exposure is materially narrower than the AV:N vector implies, and no public exploit code or confirmed active exploitation was identified at time of analysis (the flaw itself needs no user interaction or non-default toggle once the endpoint is reachable).
Absolute plot names passed to MatplotlibDataset.save() in kedro-datasets 9.3.0 through 9.6.0 let an authenticated user with the ability to influence plot-name keys write files outside the configured dataset directory, overwriting or creating files anywhere the Kedro process has write access. The flaw is rooted in validate_sub_path(), which strips leading slashes before validation, combined with pathlib join semantics that discard the base path whenever the supplied sub-path is absolute (POSIX '/outside.png', Windows 'C:\\outside.png', or UNC '\\\\server\\share\\outside.png'). Integrity impact is rated High (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N; CVSS 4.0 base 7.1), no public exploit code has been identified at time of analysis, and no CISA KEV entry exists; exploitability is gated by the attacker's ability to inject the plot-name keys (e.g., through untrusted input data or catalog configuration) and by the write permissions of the process running Kedro.
Path traversal in NetLicensing MCP Server versions prior to 0.1.8 allows an authenticated MCP client holding a valid but non-administrative NetLicensing API key to redirect the netlicensing_get_product lookup away from the intended product endpoint and onto the /token endpoint by supplying '../token' (or percent-encoded equivalents such as '..%2ftoken') as the product_number. Because the traversed response is serialized through the generic _wrap_json wrapper instead of _wrap_json_token_read, the redact_token_read() masking of APIKEY 'number' and SHOP 'shopURL' fields never runs, so plaintext token values - including admin-level credentials if present in the account - are returned in the tool output. No vendor patch is available below 0.1.8, where the issue is fixed; it is a confirmed privilege-escalation-by-credential-disclosure vector rather than direct code execution, and no public exploit has been identified at time of analysis beyond the exact payload documented in the vendor advisory.
Authenticated path traversal in Lychee photo-management tool prior to 7.6.4 allows any logged-in user to read files accessible to the web process - including the application's .env file with APP_KEY and database credentials, and other users' private images - by sending encoded traversal segments to GET /image/{path}. Exploitation is not unconditional: it requires the supported but non-default configuration with temporary_image_link_enabled on and both temporary_image_link_when_logged_in and secure_image_link_enabled off, so default installations do not expose the vulnerable code path in an exploitable state. The impact is read-only information disclosure (no write or availability effect) and disclosure of APP_KEY or DB credentials can escalate to further compromise; no public exploit was identified at time of analysis, and the vendor fixed the flaw in 7.6.4.
Path traversal in wildfly-core's deployment content handler allows an authenticated JBoss EAP, WildFly, Fuse 7, or Single Sign-On 7 user who holds the Deployer RBAC role to escape the restricted deployment directory and create files with attacker-controlled content or delete arbitrary directories on the server, escalating to full management SuperUser privileges. Exploitation requires that the Deployer role be delegated to the attacker (CVSS vector shows PR:L - authenticated, not anonymous) plus a crafted deployment name containing traversal sequences; environments that reserve the Deployer role for fully trusted administrators face little practical exposure. No public exploit code was identified at time of analysis and the flaw is not listed in CISA KEV, so this is a credible, actionable priority rather than an emergency.
Unauthenticated path traversal in the report blob endpoint of JetBrains Datalore before version 2026.2.1 allows a remote attacker who can reach the service to read arbitrary files accessible to the Datalore process. Per the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, base 7.5 HIGH), exploitation requires no credentials and no user interaction, making exposure the primary limiting factor: only network-reachable instances below 2026.2.1 are at risk, and the flaw yields confidentiality loss only, with no integrity or availability impact and no code execution on its own. There is no CISA KEV listing and no public exploit code identified at time of analysis, though the low-complexity, unauthenticated nature of the bug makes it an attractive target for opportunistic scanning of internet-facing deployments.
Root-level code execution on OPNsense firewalls running versions prior to 26.1.11 is achievable by an authenticated operator who holds the 'Firewall Alias Edit' privilege and can point a GeoIP alias at an attacker-controlled source URL. The GeoIP importer's process_zip() and process_gzip() routines trust the CSV country_code field when building output filenames under /usr/local/share/GeoIP/alias, so a crafted value traverses out of that directory and writes attacker-controlled files as root; chaining a planted newsyslog fragment with an oversized log file then lets the default hourly root cron job execute the payload, yielding complete firewall compromise (CVSS 9.9, AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H). No public exploit code and no confirmed active exploitation were identified at time of analysis, and exploitation requires a non-default alias configuration that the operator must supply.
Local privilege escalation in TotalAV versions up to 7.1.17 allows an authenticated but unprivileged local user to impersonate the SYSTEM service by forging a gRPC IPC authentication token, leading to arbitrary code execution as NT AUTHORITY\SYSTEM. Publicly available exploit code exists (a proof-of-concept C file is linked in the disclosure), though CISA KEV does not list the vulnerability as actively exploited, and the SSVC assessment rates exploitation as 'poc' with total technical impact. Exploitation requires a local foothold and the vulnerable TotalAV service to be running; it cannot be triggered remotely or against hosts without TotalAV.
Path traversal in PeaZip's archive object preview handler allows a crafted archive entry to escape the extraction directory and be handed directly to ShellExecuteW, so a victim who opens a malicious archive on Windows and invokes 'Preview with... -> Associated application' (Shift+Ctrl+O) on the rogue entry can be made to launch an arbitrary program already present on their system without the usual dangerous-extension warning. Affected are PeaZip 11.2.0 and earlier on Windows; no authentication or elevated privileges are needed, but exploitation is interaction-gated (local file delivery plus a deliberate multi-step preview action, CVSS 4.0 base 8.4 with AV:L/UI:A/PR:N and high C/I/A impact). A proof of concept was demonstrated against official vendor builds on two archive formats (.zip and .tar), confirming the defect is in PeaZip's own path handling rather than a single format parser; no CISA KEV entry or independent confirmation of active exploitation was reported at time of analysis. The practical limitation is that the flaw launches programs that already exist at the resolved path (for example a system binary) rather than dropping new attacker-supplied binaries.
Path traversal in QNAP Qsirch lets remote attackers reach the full-text search application without authentication and read files and system data outside the intended directory structure on the host NAS. The vendor states the flaw is fixed in Qsirch 7.0.3.0 and later, so only NAS devices running an earlier build of this optional app - and exposing its web interface to the attacker's network path - remain at risk; no public exploit code and no confirmed active exploitation were identified at time of analysis. Our independent assessment scores the issue at CVSS 3.1 8.6-class severity on the confidentiality axis (C:H/I:N/A:N), meaning the realistic worst case is read-only disclosure of sensitive files rather than the file modification or service disruption implied by the higher input CVSS 4.0 score of 9.3.
Authenticated path traversal in QNAP QuMagie lets an attacker who already holds a QuMagie administrator account read files and system data outside the intended media library on the underlying QNAP NAS. The flaw is remote, network-reachable and low-complexity, but the PR:H privilege requirement in the CVSS vector means it is not exploitable by anonymous users against default installations; no public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV. QNAP has shipped a fix in QuMagie 2.9.1 and later, so exposure is limited to NAS deployments still running older QuMagie builds and reachable by an admin-level account.
Authenticated path traversal in QNAP Video Station before 5.8.8 allows a remote attacker with a valid low-privileged user account to read arbitrary files and system data outside the intended application directory. The flaw is CWE-22 and requires network access with low complexity and no user interaction, but the PR:L vector means an attacker must first hold a Video Station account, limiting mass exploitation. no public exploit identified at time of analysis, and QNAP has released Video Station 5.8.8 as the fix. The vendor CVSS 4.0 score is 8.7, but independent assessment scopes impact to confidentiality only, so it is a genuine moderate-priority issue rather than a top-tier emergency.
Path traversal in QNAP Qsync Central allows an attacker who already holds a valid Qsync Central user account to read files and system data outside the intended directory scope on the NAS. The flaw originates from improper limitation of a pathname to a restricted directory (CWE-22); because the CVSS vector specifies PR:L, exploitation is authenticated - remote unauthenticated Internet attackers cannot reach it against default configurations. Impact is assessed as information disclosure of high confidentiality value rather than code execution or data destruction, and no public exploit code has been identified at time of analysis. All versions prior to Qsync Central 5.0.0.6, 5.1.0.2, and 5.2.0.4 are affected, and QNAP has released fixed builds on each of these branches.
Arbitrary file overwrite in HPE NonStop Python 3.x lets an attacker who supplies a crafted TAR archive escape the intended extraction directory via .. (dot-dot) sequences in member filenames and clobber files on the NonStop host, with the overwritten data potentially leading to code execution or system compromise depending on the privileges of the extracting process. The vendor rates this 8.0 (CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H), while our independent assessment scores it lower at CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H, treating it as local rather than adjacent-vector and integrity/availability-only; unauthenticated access is implied by PR:N in both vectors, but successful exploitation is not automatic - it requires the victim to extract an attacker-controlled archive (UI:R), and the write primitive is bounded by the privileges of the extracting account. No public exploit code was identified at time of analysis, there is no CISA KEV entry, and no EPSS score was supplied, so real-world risk is moderated by the mandatory user interaction rather than by the headline score.
Path traversal in QNAP's QcalAgent (Qcalendar) app for NAS devices lets a remote attacker who already holds a low-privileged user account read files and system data outside the intended directory. Only installations running QcalAgent 1.1.x below 1.1.10 are exposed, since the flaw is fixed in 1.1.10 and later, and the authentication prerequisite (PR:L in both the vendor CVSS 4.0 vector and our assessed CVSS 3.1 vector) means unauthenticated outsiders cannot reach it. No KEV listing and no public exploit code exists at time of analysis, but the vendor scores it 8.7 under CVSS 4.0, so patching should be prioritized wherever the optional app is installed and user accounts are shared broadly.
Authenticated path traversal in QNAP Download Station allows a remote user with a valid account to read arbitrary files outside the intended directory, potentially exposing system data. Affected versions are Download Station 5.10.x before 5.10.2.313 and 5.11.x before 5.11.3.322; the vendor has released fixes. No public exploit code or active exploitation has been identified at time of analysis, and the risk is conditional on valid credentials and network reachability to the NAS.
Unauthenticated arbitrary file read in the dbt docs serve component (dbt 2.0.0-alpha.0 through 2.0.0-alpha.4) lets any client that can reach the server POST attacker-chosen SQL to /api/v1/query and invoke DuckDB filesystem-reading functions, returning the contents of files readable by the dbt process - including paths outside the docs index directory. The SQL handler was removed entirely in 2.0.0-alpha.5. Reachability is the gating prerequisite: dbt docs serve binds to localhost by default, so remote exploitation only succeeds when an operator has exposed it via the host option or the DBT_DOCS_HOST environment variable; no public exploit code was identified at time of analysis, and no KEV listing is associated with this issue. The vector is unauthenticated (PR:N) with high confidentiality impact only (VI:N, VA:N), giving a 4.0 base score of 8.2 and an assessed 3.1 score of AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N.
Arbitrary filesystem write in Ludwig versions prior to 0.17.8: the dataset archive extraction routine (ludwig.datasets.archives.extract_archive) validates tar member names but never validates symlink or hard-link members, so a crafted archive can create a link that escapes the extraction directory and then write a later member through that link, placing attacker-controlled content at an arbitrary path with the extracting process's privileges. The same name check relied on os.path.commonprefix, a character-based comparison that also lets a sibling path sharing the destination's character prefix pass. Exploitation requires the victim to load a dataset whose configured archive URL points at an attacker-controlled or attacker-compromised tar file (CVSS 3.1: AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H - unauthenticated from the network, but mandatory user interaction), and is limited to Python 3.12 and 3.13 runtimes because Python 3.14's default tar 'data' filter already rejects escaping links; no public exploit code or confirmed active exploitation was identified at time of analysis.
Path traversal in F´ (F Prime) prior to 4.3.0 lets an authenticated peer on the file-uplink channel write or overwrite files at attacker-chosen writable filesystem locations by supplying a crafted destination path in a Fw::FilePacket::StartPacket. The flaw yields high integrity impact and limited availability impact (overwriting or damaging critical files), with no confidentiality impact, and CVSS reflects PR:L because the attacker must already be able to send file-uplink packets to Svc::FileUplink. The issue requires no non-default feature toggle once uplink access is obtained, and no public exploit code has been identified at time of analysis; vendor-released patch: 4.3.0.
Cloud Commander (cloudcmd) versions 19.20.2 through 19.21.1 expose a path traversal flaw in the GET /api/v1/pack endpoint that lets unauthenticated remote attackers read arbitrary files outside the configured --root directory, with the stolen content returned as a downloadable tar.gz archive. The root cause is a handler that calls the unguarded root() helper at server/rest/index.js:130 instead of the root.resolve() validation wrapper used on other endpoints, so percent-encoded traversal sequences in the pack path escape the intended document root and reach files such as /etc/passwd or SSH private keys. Impact is confidentiality-only (no write or code-execution primitive), and no public exploit identified at time of analysis, though a vendor patch (v19.21.2) and a public technical write-up are available; exploitation requires network reachability to the cloudcmd HTTP service, which many deployments gate behind localhost binding, a reverse proxy, or optional authentication.
Unauthenticated remote attackers can bypass access controls in the TSplus Remote Access web server via manipulated paths on the /socket.io/JWN/ endpoint, leading to disclosure of protected internal resources. This high-severity vulnerability (CVSS 4.0 base 8.7) affects internet-exposed portals with no authentication or user interaction required. No public exploit identified at time of analysis, but the flaw is trivially exploitable given network reachability.
Unauthenticated local file inclusion in the Ultimate Multisite WordPress plugin before 2.17.2 allows remote attackers to traverse the filesystem and read arbitrary local files, including wp-config.php with its database credentials and authentication salts. The plugin passes a user-supplied file-selection value directly into an include operation without validation, and the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N) confirms no authentication and no user interaction are required. Publicly available exploit code exists, but EPSS is low at 0.20% (10th percentile) and CISA SSVC records no known exploitation, so real-world risk is concentrated in internet-reachable WordPress sites that have the plugin active.
A path traversal flaw in Adobe ColdFusion's Remote Development Services (RDS) component allows arbitrary file system read outside the intended directory scope, exposing configuration files, credential stores and source code on servers where RDS is reachable. Affected builds are ColdFusion 2023 up to and including 2023.0.25 and ColdFusion 2025 up to and including 2025.0.13; per the CVSS vector (PR:N/UI:N) no credentials or user interaction are required once RDS is accessible, so the practical gate is deployment mode rather than authentication. Adobe scores this 9.3 Critical (CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H), but our reassessment scores it CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N because RDS is network-reachable on exposed servers while the integrity and availability components are not supported by the path-traversal-to-file-read primitive; no public exploit code and no confirmed active exploitation were identified at time of analysis, and real-world exposure is limited to dev, staging or legacy servers that have left RDS enabled (Production Secure Profile disables it automatically).
Authenticated path traversal in Omnispace Agora Project before 26.10.0 lets a low-privileged user write attacker-controlled files outside the intended upload temporary directory by supplying an unanchored tmpFolderName value in the upload destination path; pointing it at the web root can yield remote code execution if the written file is executable from that location. Per the CVSS vector (PR:L), a valid low-privileged account on the Agora web application is required, so exposure is materially lower on instances with restricted account provisioning or closed self-registration, and versions 26.10.0 and later are unaffected. CVSS 8.7 (v4.0) reflects high confidentiality, integrity and availability impact; no public exploit code or confirmed active exploitation was identified at time of analysis, and a vendor patch (26.10.0) is available.
Arbitrary file-system write in Adobe Experience Manager 6.5 (through 6.5.25) and AEM 6.5 LTS (through LTS SP3) allows an authenticated low-privileged attacker to place files in unauthorized locations on the host by sending a crafted request that manipulates a pathname and escapes the intended directory. No user interaction is required and attack complexity is low, but the attacker must already hold a valid low-privilege AEM account and be able to reach the instance over the network; the assessed vector (AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N) shows a scope change with high integrity impact and no direct confidentiality or availability impact. No public exploit code and no confirmed active exploitation were identified at time of analysis, so this is a credentialed post-authentication persistence and integrity risk rather than an opportunistic internet-wide exploit, though it is a credible escalation step for anyone who already has a foothold in AEM.
Remote code execution in Visual Studio Code (versions 1.0.0 up to but not including 1.141.1) is achievable through a path traversal flaw when a victim opens a crafted workspace, folder, or repository containing malicious pathnames that escape the intended restricted directory. The attack is unauthenticated (PR:N) but requires user interaction (UI:R), and the scope change (S:C) alongside high confidentiality, integrity, and availability impacts yields a CVSS score of 9.6. Microsoft has released a vendor patch (1.141.1); no public exploit code has been identified at time of analysis, though the severity warrants prompt patching.
Relative path traversal in OpenSSH for Windows (CWE-23) can allow an unauthenticated remote attacker to escape intended directories during an SSH interaction and, ultimately, execute code on the affected host - carrying a CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) and rated by SSVC as having total technical impact. Exploitation is not attacker-autonomous: it requires the victim to use the OpenSSH for Windows component and to initiate or accept an SSH connection to an attacker-controlled or compromised endpoint (the UI:R user-interaction requirement), and the host must be running a build below its fixed release (for example Windows 11 24H2 below 10.0.26100.9711 or Windows Server 2022 below 10.0.20348.5761). Current intelligence shows no public exploit identified at time of analysis, SSVC exploitation status of 'none', and non-automatable delivery, so this is a high-priority-on-paper issue whose real-world urgency is tempered by the lack of confirmed exploitation - vendor patches are available per the Microsoft advisory and should still be prioritized.
Local privilege escalation in Windows Shell allows an authenticated attacker who already holds low-privileged code execution on a Windows host to elevate to SYSTEM-level rights by supplying a crafted relative path to a privileged shell operation, causing path-traversal sequences to escape the intended directory (CWE-23, CVSS 3.1 7.8, AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Affected are default installations of the Windows client and server builds enumerated in the vendor and EUVD data, spanning Windows 10 1607 through 22H2, Windows 11 23H2 through 26H2, and Windows Server 2012 through 2025, including Server Core variants. There is no public exploit identified at time of analysis and CISA's SSVC decision framework records exploitation as none with automatable set to no, so this is a patch-priority item rather than an emergency; vendor patches are available and no user interaction is required once the attacker has local access.
Privilege elevation in the Windows Encrypting File System (EFS) lets an authenticated remote attacker supply an absolute path that EFS resolves outside its intended directory, yielding high impact across confidentiality, integrity, and availability (CVSS 8.8, CWE-36). Every supported Windows client and server generation is affected - Windows 10 (1607 through 22H2), Windows 11 (23H2 through 26H2), and Windows Server 2012, 2012 R2, 2016, 2019, 2022, and 2025, including Server Core installations - while exploitation requires the attacker to already hold valid low-privilege credentials and network reachability to the EFS service (PR:L, AV:N), with no user interaction needed. No public exploit code and no confirmed active exploitation have been identified at time of analysis per CISA's SSVC (Exploitation: none, Automatable: no), though the assessed technical impact is total; Microsoft has shipped vendor patches.
Path traversal in Skype for Business Server allows an authenticated attacker to elevate privileges over the network by exploiting absolute path traversal (CWE-36). Affected versions include Skype for Business Server 2019 CU8 below build 7.0.2046.583, Subscription Edition CU1 below build 7.0.2046.889, and 2015 CU13 below build 6.0.9319.886. No public exploit identified at time of analysis, and CISA SSVC rates exploitation as 'none' with 'Automatable: no', though the required authentication limits real-world risk.
Path traversal in on-premises Skype for Business Server (including the Microsoft Lync lineage) lets an attacker who already holds a low-privileged authenticated account on the service send a crafted network request containing an absolute file path and achieve code execution, scoring CVSS 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Affected builds are Skype for Business Server Subscription Edition before 7.0.2046.889, Skype for Business Server 2015 CU13 before 6.0.9319.886, and Skype for Business Server 2019 CU8 before 7.0.2046.583; the PR:L prerequisite means this is not a pre-auth remote exploit, so realistic risk concentrates on insiders or attackers who have already obtained a valid credential or foothold. No public exploit code has been identified at time of analysis, CISA SSVC rates exploitation as none and the flaw as non-automatable, and though no EPSS score was supplied, the total technical impact combined with an available vendor patch makes prompt upgrading the priority. This is a credible, actionable priority rather than an inflated-CVSS artifact.
Local privilege escalation in Windows Shell allows an attacker who already holds a low-privileged, authenticated account on a Windows host to traverse relative paths and raise their privileges to a higher integrity level (CVSS 3.1 base 7.8, AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Exploitation is not a remote or initial-access vector - it requires existing local code execution or account access, but needs no user interaction and is low-complexity once that foothold exists. CISA's SSVC assessment records no observed exploitation and no automatable path, and no public exploit has been identified at time of analysis; vendor patches are available, making this a credible but second-tier prioritization compared with actively exploited or remotely reachable issues.
Path traversal in .NET (CWE-22) allows an authenticated local attacker to escape an intended restricted directory and elevate privileges on the host, with the same flaw reaching users through the Visual Studio 2022 17.14 and Visual Studio 2026 18.10 toolchains. Successful exploitation requires a local, already-authenticated foothold (PR:L) plus user interaction (UI:R), meaning a higher-privileged user or process must be induced to act on an attacker-influenced pathname; it is therefore not remotely triggerable, and CISA's SSVC assessment records Exploitation: none, Automatable: no, with total technical impact if it does succeed. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV, so this rates as a moderate-priority local privilege-escalation issue rather than an urgent, widely exploitable threat. Vendor patches are available.
Authenticated path traversal in Microsoft SharePoint Server can be escalated to code execution over the network, allowing an attacker holding a valid low-privileged account to fully compromise the confidentiality, integrity, and availability of the affected deployment. On-premises installations are affected: SharePoint Server Subscription Edition below build 16.0.20326.20190, plus SharePoint Server 2019 and SharePoint Enterprise Server 2016, all of which are reachable over the network with the attacker needing only PR:L credentials and no victim interaction (AV:N/AC:L/PR:L/UI:N). There is no public exploit identified at time of analysis and CISA's SSVC assessment marks the issue as not automatable, so while impact is rated total, the authentication prerequisite and lack of automation keep this an above-average-priority rather than emergency-level issue; Microsoft has published a vendor fix.
Path traversal (CWE-22) in Microsoft Dynamics 365 Business Central lets an authenticated, low-privileged user escape an intended restricted directory through network-reachable functionality, with high confidentiality and integrity impact and a CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The required precondition is a valid low-privilege account, so anonymous exploitation is not indicated, and no user interaction or special configuration is needed once that access exists; the exact vulnerable feature or endpoint is not identified in the available description. At time of analysis there is no CISA KEV entry and no public exploit code identified, and no EPSS score was supplied, so this should be treated as a high-severity, patch-now issue driven by its privilege-escalation potential rather than by observed exploitation.
Path traversal in Microsoft Dynamics Business Central (CWE-22) allows an authenticated user holding only low-level privileges to escape an intended directory boundary and elevate privileges over the network, carrying a CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) with high confidentiality, integrity and availability impact and no user interaction required. Because the vector requires PR:L, anonymous remote attackers cannot exploit this alone - the realistic threat is insiders or holders of compromised low-privilege accounts who already possess valid credentials plus network reach to the Business Central application endpoint. No public exploit code and no confirmed active exploitation were identified at time of analysis, and the sole supplied reference is Microsoft's MSRC update guide, which is the authoritative source for fix details.
Path traversal in Fortinet FortiSIEM 7.5.0 can let a remote unauthenticated attacker execute unauthorized code or commands by sending specially crafted packets to the affected service. The CVSS vector shows network exploitation with low complexity, no privileges, and no user interaction, producing high confidentiality, integrity, and availability impact. No public exploit code or confirmed active exploitation was identified in the provided intelligence; consult Fortinet advisory FG-IR-26-180 for the authoritative affected-version and remediation details.
Unauthenticated remote attackers can write arbitrary files on servers running Risesoft-y9 Digital-Infrastructure 9.6.5 through 9.6.11 by abusing a path traversal flaw in the fileManager module's storeFile endpoint; a single crafted POST to /rest/storeFile with attacker-controlled fullPath and fileName parameters lets the service account create or overwrite files anywhere it has write permission, which can escalate to code execution if a writable path is later executed or parsed. The assessed vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H (8.8, matching the published CVSS 4.0 score), reflecting high integrity and availability impact with no confidentiality impact, and no KEV listing, so there is no confirmed active exploitation (no public exploit identified at time of analysis), though the presence of a public technical writeup and a VulnCheck advisory makes weaponization plausible. Real-world impact is bounded by the service account's write permissions and by whether the vulnerable fileManager endpoint is reachable from the attacker's network position rather than internal-only; this is a credible high-priority issue rather than a high-CVSS-but-low-risk paper cut.
Unauthenticated path traversal in Risesoft Digital-Infrastructure 9.6.5 through 9.6.11 lets any network-reachable attacker read arbitrary files from the server by placing parent-directory ('../') segments in the fullPath and fileName parameters of the fileManager /rest/retrieveFileStream endpoint, which is unauthenticated by design and backed by the Y9FileController.retrieveFileStream handler. Because the traversable location includes application configuration such as application.yml, successful exploitation exposes database, Redis and Nacos credentials - high confidentiality impact with no write or code-execution component. Both the vendor-source reference and the assessed CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N vector (7.5) confirm no authentication or user interaction is required; no public exploit identified at time of analysis, though a public technical write-up describing the traversal is referenced by VulnCheck.
Ivanti Xtraction versions prior to 2026.4 are vulnerable to a path traversal flaw in the template export feature, allowing an authenticated attacker with low privileges to read arbitrary files accessible to the service account. Exploitation requires a valid session but no user interaction, and while confidentiality is compromised, no public exploit code or active exploitation has been identified; this is a genuine but second-tier priority rather than an emergency.
Path traversal in Commvault HyperScale MediaAgents allows an authenticated low-privileged user to read files outside the intended directory over the network, resulting in unauthorized disclosure of data (rated 7.1, confidentiality-only impact with no integrity or availability effect). The flaw requires a valid session to the MediaAgent service (PR:L per the assessed vector), so anonymous internet attackers cannot trigger it - stolen, shared, or insider credentials are the realistic precondition. No public exploit code and no confirmed active exploitation were identified at time of analysis, and Commvault reports that software customers should upgrade to the resolved maintenance release; exact affected versions and deployment modes should be confirmed against advisory CV_2026_10_8.
Path traversal in the Wazuh Manager cluster upload handlers (upload_list_file, upload_rule_file, upload_decoder_file) lets an attacker who holds the cluster authentication key write files to arbitrary paths on the manager as the wazuh user, with '../' sequences in the filename parameter slipping past REST controller validation. Affected versions are Wazuh 4.1.1 through 4.14.7 (fixed in 4.14.8); exploitation requires the manager to be running in cluster mode and the actor to already possess the shared cluster key, so this is a post-compromise/lateral-movement primitive against clustered deployments rather than an internet-facing unauthenticated bug. No public exploit code has been identified at time of analysis and the flaw is not confirmed actively exploited (not in CISA KEV), but the integrity and availability impact is high once the key prerequisite is met, and the vendor has shipped a patch.
Path traversal in Wazuh Manager 4.1.1 through 4.14.7 lets an attacker who has already compromised a cluster worker node read or delete arbitrary files on the cluster master - including rbac.db - by sending traversal or absolute-path filenames through the internal cluster RPC channel. The flaw is a post-compromise, lateral-escalation primitive: it requires a multi-node deployment, adjacent network position inside the cluster, and high worker-level privileges (PR:H), and it bypasses the REST API's filename validation and RBAC enforcement because the equivalent REST endpoints do validate paths. No public exploit code or confirmed active exploitation was identified at time of analysis, and the vendor has released a patch in Wazuh 4.14.8.
Path traversal in Wazuh Manager's delete_rule_file and delete_decoder_file helpers lets an attacker who holds the Wazuh cluster key delete arbitrary files as the wazuh user, including ossec.conf, client.keys, and rule files. Affected versions are 4.1.1 through 4.14.7 (fixed in 4.14.8), tracked by CPE cpe:2.3:a:wazuh:wazuh-manager. Exploitation is not unauthenticated: the CVSS 4.0 vector carries PR:H and the assessed 3.1 vector is AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H, meaning the attacker must already possess the cluster key and be able to invoke the DistributedAPI helpers as a cluster worker, so practical exposure is limited to clustered multi-node Manager deployments where the key has leaked or a worker node is compromised; no public exploit code was identified at time of analysis and there is no confirmed active exploitation (CISA KEV).
Path traversal in NLTK's WekaClassifier integration (all versions through 3.10.3) lets attackers who control the model_filename or model argument escape nltk.pathsec containment and drive the Weka JVM to write files outside permitted data roots via the -d option, or probe for file existence via -l. There is no public exploit identified at time of analysis and the flaw is not confirmed actively exploited (CISA KEV), but exploitation requires an application that wires attacker-controllable values into WekaClassifier and has a working Weka Java/JVM toolchain installed - a non-default, niche integration that most NLTK deployments never invoke. Under those preconditions, the CVSS 4.0 base score of 8.3 is driven by a network vector with high integrity impact (VI:H), while the AT:P metric reflects the required application-wiring precondition.
Path traversal in the NVIDIA AIStore for Linux dSort archive extraction component allows a remote attacker to write files outside the intended extraction directory by submitting a dSort job that references an archive (e.g., tar/zip) whose member names contain crafted traversal sequences, yielding arbitrary file creation or overwrite and potentially code execution, information disclosure, data tampering, and denial of service. The vulnerability carries a CVSS 3.1 base score of 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) per the assessed vector, indicating remote reachability and no authentication requirement, but a high attack-complexity rating that reflects the difficulty of reliably crafting the malicious archive and triggering the flaw. There is no confirmed active exploitation (CISA KEV) and no public exploit code identified at time of analysis; the practical gating factor is network access to the AIStore dSort/API endpoint, which in typical deployments is confined to a trusted ML/training cluster or private network rather than being internet-facing. Because the dSort job-submission path is the attack surface, exposure is primarily amplified where AIStore's API is reachable from untrusted networks, and no user interaction is required.
Unauthenticated path traversal in the NVIDIA AIStore Promote API on Linux lets a remote attacker read arbitrary files that the AIStore process can access by supplying a crafted absolute source path, resulting in high-confidentiality information disclosure (CVSS 3.1 base 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N). Any network-reachable deployment where the Promote endpoint is enabled and functional is at risk, since the vector requires no authentication (PR:N) and no user interaction (UI:N). No public exploit code and no confirmed active exploitation were identified at time of analysis; the practical blast radius is bounded by the OS privileges of the AIStore process account and by whether the Promote API is exposed beyond trusted internal networks, making this a genuine but moderate-priority issue rather than a critical emergency.
Unauthenticated path traversal in the target-side object rename handler of NVIDIA AIStore on Linux allows a remote attacker who can reach a target (storage) node directly to write files outside the intended storage directory by supplying a crafted rename destination, resulting in arbitrary file creation or overwrite. NVIDIA rates the issue CVSS 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, CWE-22), with downstream consequences that could include code execution, privilege escalation, information disclosure, data tampering, and denial of service depending on what the overwritten path controls. Exploitation is constrained rather than trivial: the attacker needs network reachability to a target node - not merely the front-end proxy - and must build a traversal payload the rename handler accepts, so exposure is greatest in flat cluster networks or environments where target ports are directly reachable; no public exploit code and no CISA KEV entry were identified at time of analysis.
Path traversal in the Siemens .NET Client Library for the SIMATIC S7 Webserver API (all versions prior to V3.3.61) lets a remote attacker who controls or man-in-the-middles the server that the client downloads tickets from specify a crafted filename and thereby write arbitrary files outside the intended download directory. Integrity impact is high (VI:H) while confidentiality and availability impacts are none, consistent with the vendor's CVSS 4.0 base score of 8.7; the CVSS vector indicates no privileges (PR:N) or user interaction (UI:N) are required, so the only real prerequisite is that the attacker already occupies the server/MITM position relative to the victim client. The additional ability to replace existing files is limited to deployments where file overwriting is enabled. No public exploit code was identified at time of analysis and there is no indication of confirmed active exploitation.
Directory traversal in the iKuai8 management interface shipped on the IK-Q3000 Enterprise-grade Wi-Fi 6 router lets an attacker escape the intended file path and execute arbitrary code on the device; affected builds are Enterprise Edition <= iKuai8_3.7.23_Enterprise Build 202606021825 and Free Edition <= iKuai 8_4.0.304-beta. The CVE record scores this 9.8 with a PR:N vector (unauthenticated), but the public disclosure is explicitly titled 'authorized' path traversal and our independent assessment rates it PR:L, so a valid authenticated management session is most likely a prerequisite and is the key factor limiting real-world exploitation. There is no CISA KEV entry and no public exploit identified at time of analysis, and EPSS is low at 0.45% (38th percentile); exposure is further gated by network reachability to the router's administrative web service, so units with management bound to an internal/LAN interface are materially less exposed.
Authenticated remote code execution in IBM TRIRIGA Application Platform 5.0.0 through 5.0.8 arises from improper validation of file paths inside archives the platform extracts, allowing an attacker with a valid account to write files to arbitrary locations and execute code under the privileges of the TRIRIGA service (CVSS 3.1: 8.8, AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The attack is network-reachable with no user interaction and low complexity, but the PR:L vector gates it behind an existing authenticated session, confining realistic exploitation to insiders or attackers who have already obtained platform credentials. No public exploit identified at time of analysis, and IBM has published a vendor patch advisory covering the affected 5.0.0-5.0.8 range.
Arbitrary file write via path traversal in IBM Planning Analytics 2.0 and 2.1 allows remote unauthenticated attackers to write files to arbitrary locations on the server by submitting a crafted URL containing '/../' sequences. The vulnerability carries a CVSS 3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N), indicating high integrity impact but no confidentiality or availability impact. A vendor patch is available per IBM support node 7291604, and no public exploit identified at time of analysis.
Path traversal in IBM Planning Analytics 2.0 and 2.1 allows a remote attacker to read arbitrary files from the host and overwrite certain application files by supplying crafted file paths to the service. The CVSS 3.1 vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N, base 8.2) confirms network reachability, low attack complexity, no authentication requirement (PR:N), and no user interaction, with high confidentiality impact and limited integrity impact. No public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis; the vendor has released a fix referenced in the IBM advisory.
Denial of service in IBM DataStage on Cloud Pak for Data 5.4.0.0 can be triggered by a remote user who already holds valid platform credentials and supplies path traversal sequences to the product's file-handling logic, disrupting or halting the service. Exploitation requires an authenticated session with low privileges (CVSS vector PR:L) and no action by a victim, so the practical barrier is credential access rather than network reachability; availability is the realistic impact, with no evidence of code execution. A vendor patch is available via IBM support advisory node 7288649, and no public exploit code or confirmed active exploitation was identified at time of analysis.
Authenticated path traversal in IBM DataStage on Cloud Pak for Data 5.4.0.0 allows a remote attacker holding a valid platform account to bypass intended directory restrictions and execute arbitrary code. Exploitation requires only low-privileged credentials (CVSS PR:L), needs no user interaction, and is network-reachable with low complexity, which is why the vector scores 9.9 Critical with a scope change (S:C) reflecting impact that can extend beyond the vulnerable component. Despite the high score, the practical risk picture is more moderate: EPSS is only 0.49% (40th percentile), CISA SSVC rates exploitation as none with automatable set to no, there is no public exploit code identified at time of analysis and no KEV listing, and the vendor has published a patch, so remediation is available rather than dependent on compensating controls alone.
Path traversal in IBM Maximo Application Suite 8.10, 8.11, 9.0, 9.1 and 9.2 lets remote, unauthenticated attackers read arbitrary files from the server by sending crafted URL requests containing '../' sequences. The flaw carries a CVSS 3.1 score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), so impact is confined to confidentiality with no data modification or denial of service, and the independent assessment rates the overall signal as moderate and internally consistent rather than alarming. No public exploit code was identified at time of analysis and the CVE is not listed in CISA KEV; practical exposure depends mainly on internet reachability and on the OS-level file permissions of the account running the Maximo web process, since only files that account can read are disclosed.
Path traversal in ConvertX (all releases prior to 0.18.0) lets an authenticated user write converted output files to arbitrary paths inside the container by supplying traversal sequences in the convert_to parameter of the /convert endpoint. The CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H reflects that exploitation requires a valid account by default, though instances deliberately configured for unauthenticated access lower that bar to anyone who can reach the service; the payoff is integrity and availability impact - overwriting files or causing denial of service - rather than data disclosure. A vendor fix is available in 0.18.0 (upstream PR 532, commit 0965928), and no public exploit code or confirmed active exploitation was identified at time of analysis, keeping this a credible above-average-priority issue rather than a top-tier emergency.
Authenticated users of the MarkLogic Query Console can read arbitrary files from the underlying server by supplying unsafe path values to a privileged filesystem helper, a classic path-traversal disclosure (CWE-22). The issue affects MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7, and carries a CVSS 3.1 base score of 7.7 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N), meaning a network-reachable, low-complexity attack by an authenticated principal that yields high confidentiality impact with no integrity or availability effect and a scope change because the helper runs with privileges beyond the caller's own. Because exploitation requires valid Query Console credentials, this is a credible moderate-to-high priority patching item rather than a drop-everything emergency; no public exploit code or confirmed active exploitation was identified at time of analysis.
Path traversal in the legacy InfoStudio modules shipped with Progress MarkLogic Server lets a low-privileged authenticated remote attacker reach files outside the intended module directory and, because user-context values are also insufficiently validated, potentially have code run under an unintended identity. Affected deployments are MarkLogic Server 12.x releases before 12.1.0 and 11.x releases before 11.3.7 that still have the legacy InfoStudio modules present and reachable. The vendor rates this 8.5 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N), reflecting a confidentiality-first impact that crosses a security boundary; no public exploit code has been identified at time of analysis and the flaw is not confirmed as actively exploited, but fixed builds are already available, so this is a priority patching item rather than an emergency.
A path traversal flaw in rebar3, the standard build and dependency-management tool for Erlang/OTP, lets a malicious Hex package publisher cause rebar3 to delete an arbitrary directory and write package files into it whenever a developer or CI job fetches that package's dependencies. The attack abuses an unvalidated 'app' field in Hex registry dependency metadata: rebar3 treats that field as the dependency directory name, so a value such as '../../../../target' resolves outside the project's _build tree and is then removed with rm -rf before the fetched package is moved into place. Only rebar3 3.7.0-rc1 through 3.27.1 is affected, exploitation requires user interaction (a developer running rebar3 get-deps against a project that pulls in the malicious release, directly or transitively), and because the deletion occurs before the dependency's rebar.config.script is evaluated and get-deps compiles nothing, the practical impact is destructive file deletion and overwrite rather than immediate code execution; no public exploit code has been identified at time of analysis, and the public hex.pm registry added validation for the field on 2026-10-12, leaving private or self-hosted Hex registries as the main residual exposure.
Path traversal in the Hex package manager for the Elixir/Erlang (Mix) ecosystem, versions 0.6.0 through 2.5.1, lets a malicious package publisher delete a directory outside the project's deps/ folder and write the package's files into that location when a developer runs mix deps.get or mix deps.update. The attacker abuses a dependency's OTP application label, which Hex copies from the signed registry without validation and Mix joins onto deps/ as the checkout path, so a crafted label such as '../../target' escapes the project tree through File.rm_rf!/1 before any dependency code is compiled. Exploitation requires the victim project to depend directly or transitively on the attacker-controlled release and the developer to explicitly fetch dependencies, so no victim-side authentication is needed (PR:N) but user interaction is required; no public exploit identified at time of analysis, and the vendor rates it CVSS 7.5.
Authenticated back-office users of Thelia through 2.6.1 can chain a path traversal flaw in the translation editor with a PHP string-escaping failure to write and execute arbitrary PHP code on the server, achieving remote code execution with web-server privileges. The attack requires a back-office account holding UPDATE-level permission on the admin.configuration.language resource (CVSS 3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, assessed 8.8), so it is not reachable by unauthenticated or low-privilege users despite the network attack vector; no public exploit code and no confirmed active exploitation were identified at time of analysis, and EPSS is low at 0.47% (39th percentile), making this a high-impact but moderate real-world priority.
Arbitrary file write in Progress ShareFile Storage Zones Controller 5.12.6 and earlier lets an unauthenticated remote attacker who can influence the remote file identifier consumed by FileCopyService place attacker-controlled content into any filesystem location writable by the Storage Zones service account. Escalating that write to remote code execution requires a second, non-default condition: an IIS-served directory that is both executable and writable by that same account, which is why the assessed attack complexity is high. No public exploit code has been identified at time of analysis, and the risk profile is configuration-dependent rather than a mass-exploitation emergency.
Path traversal in the OTRS SendSupportBundle functionality allows an authenticated administrator to delete files outside the intended directory, limited by the operating system permissions of the OTRS application process. The issue affects OTRS versions 7.0.X through 2026.X before 2026.7.X, as well as ((OTRS)) Community Edition 6.x and earlier; products based on Community Edition are likely affected. Despite a high CVSS score of 8.7, exploitation requires a valid administrative account and does not bypass OS file permissions, and no public exploit has been identified.
Persistent code execution on a penetration tester's workstation is achievable through a relative path traversal (CWE-22) in the Metasploit Framework post module post/apple_ios/gather/ios_image_gather, affecting versions prior to 6.5.5. A hostile or tampered iOS device can return a crafted directory-listing entry (for example ../../msfconsole.rc) that the module interpolates without sanitization into the local destination path handed to client.fs.file.download_file(), overwriting ~/.msf4/msfconsole.rc, which every msfconsole invocation automatically executes at startup; because the written resource file can load a second written Ruby plugin, this converts into an interactive shell as the operator (frequently root) at the next console launch. Exploitation is not remote-unauthenticated against a default service: it requires operator interaction (UI:R) to run the specific gather module against an attacker-controlled Meterpreter session, no workstation authentication (PR:N) is needed, and the assessed attack complexity is High because the hostile device, the specific module, and the resulting file write must all align; no public exploit code was identified at time of analysis, and the flaw is fixed in the 6.5.5 release.
Authenticated users of Blinko through version 1.8.8 can achieve remote code execution as root by supplying a plugin name containing '../' sequences to the plugin.installPlugin tRPC procedure, which constructs the install path from the unsanitized name and writes downloaded plugin files outside the plugins directory. Because the official Docker image runs as root, an attacker can overwrite a root-owned startup file and gain code execution at the highest privilege level; the endpoint is open to any authenticated account and the referenced sign-in code indicates self-registration may be enabled, potentially letting an unauthenticated outsider obtain the required account. The assessed vector is CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (8.8), reflecting a genuine high-priority issue rather than a CVSS-inflated paper risk; no confirmed active exploitation is indicated by CISA KEV, though the references include a public repository dedicated to this path-traversal RCE chain that should be treated as potential exploit material.
Authenticated members of pH7Builder (pH7 Social Dating CMS) instances running versions before 18.5.0 can delete arbitrary files on the host by submitting ../ traversal sequences in the POST picture_link parameter handled by the picture module's deletePhoto() action. Because the parameter is concatenated unsanitized into the public picture storage directory, an attacker can escape that directory to remove other members' photos as well as application configuration and cache files, producing content loss and a denial-of-service condition (CVSS 3.1 base 7.1, AV:N/AC:L/PR:L/UI:N, C:N/I:H/A:H; vendor/SI scoring 7.2 under CVSS 4.0). Impact is limited to destructive deletion - there is no file read/exfiltration and no code execution path - and no public exploit code was identified at time of analysis, with no CISA KEV listing.
Arbitrary file deletion in the ChimpStudio FoodBakery WordPress theme (versions up to and including 4.6) allows an authenticated attacker holding only a Subscriber-level account to delete arbitrary files on the server, with no user interaction required. The underlying path traversal flaw (CWE-22) lets a crafted request escape the intended directory and reach sensitive files such as wp-config.php, so the scope change (S:C) escalates impact beyond availability loss toward full site compromise. Rated CVSS 7.7 (AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H); no public exploit identified at time of analysis, and exploitation is gated by whether the site permits attackers to hold a Subscriber account, which is trivial on sites with open self-registration and meaningfully harder where registration is disabled or restricted.
Authenticated subscribers can delete arbitrary files on WordPress sites running PeepSo versions up to 9.0.5.4 due to a path traversal flaw (CWE-22). This high-severity (CVSS 7.7) vulnerability requires only a low-privilege account, which is easily obtained on sites with open registration, and allows deletion of critical files, potentially leading to site compromise or denial of service. No public exploit code has been identified at time of analysis.
Attackers can delete arbitrary files outside the intended directory in rtMedia for WordPress, BuddyPress and bbPress (buddypress-media) versions up to 4.7.13 due to a path traversal flaw, causing high integrity and availability impact. The published CVSS score is 9.8, but our assessment indicates a likely authenticated vector (PR:L) and no confidentiality impact; authentication requirements are not confirmed from available data. No public exploit code or active exploitation has been identified at time of analysis.
Unauthenticated arbitrary file read affects the Divi Plus plugin for WordPress through version 2.4.0, letting any remote attacker retrieve files from the web server via the svg_image parameter of the /wp-json/elicus/v1/dipl-modules/svg-animator REST endpoint. The endpoint's permission callback returns true unconditionally and the input checks used (sanitize_text_field() and esc_html()) do not block filesystem paths, the file:// stream wrapper, or arbitrary URLs, so the raw contents of the targeted file are returned in the JSON 'html' field; the issue is rated CVSS 3.1 7.5 HIGH (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N). No public exploit code has been identified at time of analysis, and no EPSS score or CISA KEV listing was provided, but successful reads of sensitive files such as wp-config.php could enable follow-on remote code execution.
Unauthenticated remote attackers can delete arbitrary files on WordPress/WooCommerce sites running the PPOM - Product Addons & Custom Fields for WooCommerce plugin through version 34.0.10, abusing insufficient path validation in the rename_files function that is reachable via the plugin's cart/order file-handling path. Removing critical files such as wp-config.php can push the site into a re-installation state that is readily leveraged for remote code execution, and because the relocated file is moved byte-identically into the web-accessible wp-content/uploads/ppom_files/confirmed/ directory, the same flaw also exposes arbitrary file read for anything the web server user can read. Wordfence rates it 9.1 and independent assessment confirms CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, i.e. no authentication, privileges, or user interaction required against default internet-exposed configurations; no public exploit code has been identified at time of analysis. This is a genuine high-priority issue, not a CVSS-inflated one, with the main precondition being simply that the vulnerable plugin version is installed, active, and serving requests.
Path traversal in plugNmeet Server through 2.5.2 allows any authenticated meeting participant to read arbitrary files from the host by supplying crafted ../ sequences in the filePath value passed to the whiteboard document-conversion endpoint; the resulting page images are then retrievable without authentication via /download/uploadedFile/. The assessed impact is confidentiality-only (high file read, no write or availability effect) against the server process's readable files, and publicly available exploit code exists - though there is no CISA KEV listing, so this is best treated as a moderate-priority information-disclosure issue rather than a critical emergency. Risk is highest where the plugNmeet process can read secrets, configuration files, or credentials on the same host.
Path traversal in KodExplorer before 4.55 lets an authenticated low-privileged user bypass the archive-extraction sanitizer and write files anywhere on the server by uploading a ZIP archive containing crafted names such as '....//'. Because the overwritten files can include core JavaScript assets, the flaw chains into stored XSS that can lead to administrator account takeover and, ultimately, remote code execution through unrestricted PHP file upload. Exploitation requires a valid low-privileged account and use of the unzip functionality, so this is a credible, actionable priority rather than a drop-everything emergency; no public exploit code has been identified at time of analysis and no CISA KEV entry confirms active exploitation, while a vendor patch is available in release 4.55.
Path traversal in Apache Camel Karavan 3.18.0 through 4.22.0 allows an authenticated user of any role to write arbitrary files outside the project directory by supplying a project file name containing '../' sequences, leading to overwrite of application configuration or classpath files and potential remote code execution in the Karavan container. The flaw is present in default behavior and requires only a valid account (CVSS 8.8, PR:L). No public exploit code or active exploitation has been identified at time of analysis, but the high impact and low privilege requirement make this a genuine high-priority issue.
Unauthenticated remote attackers can read arbitrary files from the underlying web server by exploiting a path traversal flaw in the WordPress plugin PDF for Contact Form 7 (slug pdf-for-contact-form-7) affecting all versions through 7.1.0. Supplying crafted directory-traversal input to the plugin's PDF file-handling/download path lets an attacker escape the intended directory and retrieve files readable by the web server account, a high confidentiality impact with no integrity or availability effect (CVSS 3.1 base 7.5, AV:N/AC:L/PR:N/UI:N). No public exploit code, CISA KEV listing, or EPSS score was identified in the supplied intelligence, so exploitation has not been confirmed as active and the practical attack surface depends on the plugin being installed and activated; note that WordPress core does not ship this plugin, so exposure is limited to sites running it.
Unauthenticated path traversal in ZealousWeb's Generate PDF using Contact Form 7 WordPress plugin, affecting all releases through 4.2.1, lets a remote attacker read arbitrary files from the web server, an impact mirrored by the CVSS 3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N, C:H/I:N/A:N - confidentiality only, no integrity or availability impact). Any WordPress site with this add-on installed, active, and reachable is exposed if its PDF generation/download endpoint accepts unauthenticated requests; the practical limiting factor is the plugin's comparatively small install base rather than any authentication or configuration barrier. At time of analysis no public exploit code has been identified and there is no CISA KEV listing, but the low-complexity, unauthenticated nature of the flaw makes it a natural candidate for automated mass scanning.
Unauthenticated path traversal in gvproxy, the network forwarder shipped in the gvisor-tap-vsock package (used by Podman Desktop, Red Hat OpenShift/CRC tooling and related Red Hat products), lets an attacker who can reach the /services/forwarder/expose control endpoint supply an arbitrary socket path that is passed unsanitised to os.Remove, resulting in deletion of arbitrary files on the host. The defect is reachable without credentials (PR:N) but requires adjacent/guest-side network access to the forwarder API (AV:A), which is normally bound to the virtual network rather than exposed as a routed internet service; impact is limited to integrity and availability (no data disclosure). No public exploit code has been identified at time of analysis and the flaw is not listed as confirmed actively exploited (CISA KEV); an upstream fix exists in gvisor-tap-vsock PR #718. The vendor score of 9.3 (CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H) reflects low-complexity, unauthenticated access combined with a scope change and High integrity/availability impact, and the actual risk depends heavily on whether the forwarder control API is reachable by an untrusted guest or adjacent host.
Banks, a Python library for generating LLM prompts from a simple template language, ships a DirectoryPromptRegistry that prior to version 2.5.1 fails to reject symbolic links for its index.json file and for discovered or existing .jinja prompt files. An attacker who can influence the contents of the registry directory - for example by planting a symlink or by controlling files extracted from an untrusted archive into that directory - can cause _scan() and get() to follow a link outside the registry root and disclose arbitrary files, while set(), _save() and _load() can read or overwrite an external link target, giving high confidentiality and integrity impact with limited availability impact. Exploitation requires local placement influence over the prompt directory and applies only to deployments that use DirectoryPromptRegistry and expose that directory to untrusted input, which is why the vendor CVSS 4.0 base score is 7.3 (AV:L/AC:L/AT:P/PR:L/UI:N) and the assessed CVSS 3.1 vector is AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L; no public exploit code and no confirmed active exploitation (CISA KEV) were identified at time of analysis. The issue is fixed in version 2.5.1.
Unauthenticated path traversal in IBM Guardium Data Protection 12.0, 12.1, and 12.2 can be leveraged by remote attackers to execute arbitrary code on the affected deployment, producing a vendor CVSS 3.1 base score of 9.8 from the vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Per that vector the flaw requires no authentication, no user interaction, and no non-default configuration, so the only practical barrier is network reachability of the exposed Guardium interface; because the product is normally deployed inside segmented enterprise networks, internet-wide exposure is expected to be limited. There is no public exploit identified at time of analysis and no confirmed active exploitation, but the worst-case skill and access profile place this in the urgent patching tier for any instance reachable from untrusted networks; the specific traversal entry point and the path from traversal to code execution are not detailed in the available advisory data and should be confirmed against IBM support node 7291674.
IBM Guardium Data Protection 12.1 and 12.2.2 contain a path traversal flaw (CWE-22) that lets a remote, unauthenticated attacker delete arbitrary files on the appliance by supplying traversal-laden input to an affected file-handling function, giving a high-integrity and availability impact with no confidentiality exposure (CVSS 3.1: 9.1, AV:N/AC:L/PR:N/UI:N/C:N/I:H/A:H). No public exploit code has been identified at time of analysis, EPSS is low at 0.36% (28th percentile), and CISA's SSVC decision framework rates exploitation as 'none' with a total technical impact, so this reads as a serious but not emergency-priority issue. Practical risk is bounded by reachability: Guardium is a management-plane appliance normally confined to privileged database and security administrators behind the enterprise perimeter, which narrows the realistic attacker population despite the network-vector rating.