Security readout for executives and security teams
Plain-English summary
UpTrain 0.7.1 and earlier can let an authenticated user run arbitrary code through the /new_run endpoint. Successful exploitation could compromise the confidentiality, integrity, and availability of the UpTrain host or its container. The supplied sources report no available patch.
Executive priority
Treat this as a high-priority exposure review. Immediately identify affected deployments, reduce access, and assess potential compromise. Prioritize externally reachable or multi-user instances. Because no patch was reported, risk reduction depends on isolation, access control, least privilege, monitoring, and continued vendor-guidance tracking.
Technical view
The /new_run endpoint improperly handles the checks and metadata parameters, enabling code injection classified as CWE-74. Exploitation is network-accessible, requires low privileges, needs no user interaction, and executes code in UpTrain's host context—typically its documented Docker container.
Likely exposure
Exposure exists where UpTrain 0.7.1 or earlier is deployed and an attacker can reach the service with valid authentication. Internet-accessible, broadly shared, or weakly controlled instances warrant the fastest review. The sources do not identify affected configurations beyond the stated version and access conditions.
Exploitation context
The CVSS 4.0 score is 7.4, and its vector records proof-of-concept exploit maturity (E:P). The CVE is not listed as KEV in the supplied bundle, and no cited evidence establishes active exploitation. Authentication is required, but any valid UpTrain user may represent a threat.
Researcher notes
The affected path is /new_run, with checks and metadata identified as dangerous inputs. The vulnerability boundary is authenticated access, not anonymous access. Host impact may initially be container-scoped, but actual consequences depend on container privileges, mounts, secrets, and network reach. The supplied evidence does not establish a patched release or active exploitation.
Mitigation direction
- Inventory UpTrain deployments and identify every instance running version 0.7.1 or earlier.
- Restrict UpTrain access to trusted users and tightly controlled networks.
- Disable or isolate affected instances when access cannot be adequately restricted.
- Review vendor and advisory guidance regularly; no known patch was available at publication.
- Minimize container privileges, accessible secrets, mounted files, and network permissions.
Validation and detection
- Confirm the installed UpTrain version using trusted deployment or package records.
- Verify whether authenticated users can reach the /new_run endpoint.
- Review authentication records and remove unnecessary, shared, or untrusted accounts.
- Inspect application, container, and host logs for anomalous /new_run activity.
- Check container mounts, secrets, privileges, and network access to determine potential impact.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-74: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2025-27772 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.4 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P——GitHub_MVulnerability scoring details
Base CVSS 4.0 score
7.4HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://securitylab.github.com/advisories/GHSL-2024-200_GHSL-2024-201_Uptrain/CVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/uptrain-ai/uptrain/blob/a31cc14eddcb6c0b0b12cbed15f086d98c441c6f/uptrain/dashboard/backend/app.py#L773CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.