Loading story…
A high-severity vulnerability tracked as CVE-2026-73034 affects eosphoros-ai DB-GPT up to and including version 0.8.1, allowing unauthenticated attackers to exploit the Python file-upload endpoint by placing directory traversal sequences in the user_id HTTP header. The flaw lets remote attackers escape the intended upload directory and write arbitrary files anywhere on the server, creating broad risk to confidentiality, integrity, and availability under the published CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
Advisories warn that attackers could place controlled files in sensitive locations such as Python startup hooks, cron directories, or agent scripts, potentially escalating the arbitrary file write into remote code execution. A security patch in the DB-GPT repository hardens the upload logic by restricting user_id to alphanumeric characters, underscores, and hyphens, resolving uploads only under the python_uploads base directory, and enforcing containment checks to block traversal, TOCTOU, and symlink-based escapes; added tests also verify rejection of traversal payloads and unsafe path conditions.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
3 events from the most recent confirmed update back to the earliest known activity.
The CVE record for the DB-GPT path traversal arbitrary file write states it was newly received by disclosure@vulncheck.com and identifies affected versions up to and including 0.8.1. The entry classifies the issue as CWE-22 and notes that exploitation can lead to arbitrary file write and remote code execution.
VulnCheck published an advisory describing an unauthenticated path traversal flaw in DB-GPT v0.8.1's Python file-upload endpoint. The advisory said attackers could abuse the user_id HTTP header to write arbitrary files on the server and potentially achieve remote code execution.
A DB-GPT commit introduced validation for the user_id header in the Python file upload API, restricting allowed characters and enforcing containment checks so upload paths cannot escape the intended python_uploads directory. The patch also added tests covering traversal attempts, whitespace-padded IDs, default handling, and symlink-based escape scenarios.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
4 references tracked. Mallory keeps watching after this page renders.
cvefeed.io
Open sourcevulncheck.com
Open sourcegithub.com
Open sourcegithub.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Two high-severity vulnerabilities, **CVE-2026-35392** and **CVE-2026-35393**, were disclosed in **goshs**, a Go-based SimpleHTTPServer, affecting versions prior to **`2.0.0-beta.3`**. Both issues are classified as **CWE-22 path traversal** flaws that arise from missing pathname sanitization in file upload functionality: **PUT** upload handling in `httpserver/updown.go` and **POST multipart** upload directory processing. The weaknesses could allow remote, unauthenticated attackers to write files outside intended directories. Both CVEs carry the same **CVSS v3** vector, **`AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`**, indicating high impact to confidentiality, integrity, and availability. The vulnerabilities were addressed in **`2.0.0-beta.3`**, and related GitHub security advisories were published alongside the fixes. Organizations using goshs for file upload workflows should prioritize upgrading and review exposed instances for unauthorized file placement or tampering.
Jun 29, 2026
Two application vulnerabilities have exposed AGiXT and Bugsink servers to filesystem-level attacks that can lead to full host compromise. In AGiXT, advisory `GHSA-5gfj-64gh-mgmw` describes an authenticated path traversal flaw in the Essential Abilities Extension, rated **CVSS 8.8**, that lets an attacker escape intended directories and access files with the permissions of the AGiXT process. The issue allows arbitrary read, write, and delete operations against sensitive targets including environment files, configuration data, database credentials, cryptographic keys, `/etc/shadow`, and `.ssh/id_rsa`, creating high risk to confidentiality, integrity, and availability. A separate flaw tracked as `CVE-2026-40162` affects Bugsink and enables authenticated arbitrary file write or overwrite within the application's runtime permissions, with a **CVSS 7.1** rating. The weakness can be used to overwrite Python source files or module initialization scripts so attacker-controlled code executes on restart or when a new worker is spawned, effectively turning file access into remote code execution. Both disclosures warn that deployments running with elevated privileges or broad filesystem access face the greatest danger, including persistence through locations such as cron directories, `.ssh/authorized_keys`, or application package paths, as well as exposure of secrets, telemetry, and backend credentials.
Jun 29, 2026
FastGPT, an AI agent building platform, was disclosed with multiple high-severity vulnerabilities affecting both its application and development pipeline. **CVE-2026-33075** impacts versions `4.14.8.3` and earlier and stems from the `fastgpt-preview-image.yml` GitHub Actions workflow using `pull_request_target` while checking out untrusted fork code. The flaw allows external contributors to achieve arbitrary code execution in GitHub Actions, exfiltrate secrets, and potentially trigger a supply-chain compromise by building and pushing attacker-controlled container images to the production registry. At disclosure, no patch was available for that issue; GitHub tracked it as `GHSA-xfx8-w35j-485c`. Two additional flaws, **CVE-2026-40351** and **CVE-2026-40352**, affect FastGPT versions prior to `4.14.9.5` and were fixed in that release. Both are **NoSQL injection** bugs caused by missing runtime validation in password-handling logic. The first lets an unauthenticated attacker bypass login checks by supplying MongoDB operators such as a password object matching any value, enabling login as arbitrary users including the root administrator. The second lets an authenticated low-privileged user bypass old-password verification in the password-change endpoint, enabling unauthorized password resets and possible account takeover, with broader impact if combined with ID manipulation.
Jun 29, 2026