LiveActive security incident?Get immediate response
CVE Record

CVE-2025-27771: Uptrain vulnerable to remote code execution via `/add_prompts` endpoint

UpTrain is an open-source platform to evaluate and improve generative AI applications. In version 0.7.1 and prior, the `/add_prompts` endpoint is vulnerable to remote code execution via the `checks` and `metadata` parameters. Any user that has access to UpTrain and a valid authentication method may be able to execute arbitrary code in the context of the host running UpTrain, which in most cases will be the docker container as suggested by the documentation. As of time of publication, no known patch is available.

HighCVSS 7.4Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

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 `/add_prompts` endpoint. The code runs with the privileges of the UpTrain process, commonly inside its documented Docker container. This could expose application data, disrupt service, or enable further compromise within the container’s accessible environment.

Executive priority

Prioritize within the urgent vulnerability queue, especially for internet-reachable or broadly shared installations. Immediately reduce access and investigate suspicious authenticated activity. Because no patch was known at publication, assign ownership for vendor monitoring and compensating controls rather than assuming routine patching has resolved the risk.

Technical view

The `/add_prompts` endpoint improperly handles attacker-controlled `checks` and `metadata` parameters, resulting in CWE-74 code injection. Exploitation is network-accessible, low-complexity, requires valid authentication, and needs no user interaction. Successful exploitation compromises confidentiality, integrity, and availability in the UpTrain process context.

Likely exposure

Exposure exists where UpTrain 0.7.1 or earlier is deployed and an authenticated user can reach `/add_prompts`. Internet accessibility increases concern, but authentication is still required. Containerization may limit impact, depending on privileges, mounted secrets, network access, and host integration. The sources provide no deployment-prevalence data.

Exploitation context

The supplied CVSS 4.0 vector reports proof-of-concept exploit maturity (`E:P`). However, this CVE is not identified as CISA KEV, and the supplied sources do not establish active exploitation in the wild. Treat exposed authenticated deployments as credible targets without claiming observed campaigns.

Researcher notes

Affected versions are UpTrain 0.7.1 and earlier. The vulnerable inputs are `checks` and `metadata` on `/add_prompts`; the weakness is classified as CWE-74. The supplied material establishes arbitrary code execution in the UpTrain host-process context but does not establish container escape, unauthenticated exploitation, or broader affected products.

Mitigation direction

  • Identify and isolate every UpTrain deployment running version 0.7.1 or earlier.
  • Restrict UpTrain access to trusted users and approved internal networks.
  • Temporarily disable or tightly restrict `/add_prompts` where operationally feasible.
  • Rotate credentials if unauthorized authenticated access may have occurred.
  • Monitor vendor guidance for a supported patch or remediation; none was known at publication.

Validation and detection

  • Confirm the installed UpTrain version from authoritative deployment records or package metadata.
  • Determine whether `/add_prompts` is reachable externally or from untrusted network segments.
  • Review authentication and endpoint logs for unexpected `/add_prompts` requests.
  • Assess container privileges, mounted secrets, filesystem access, and outbound network connectivity.
  • After remediation, verify the endpoint no longer accepts unsafe parameter processing.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

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 lookup
description · low confidence lookup

Execution 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 lookup
description · low confidence lookup

Container 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 lookup
cve · low confidence lookup

CVE-2025-27771 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
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

Official CVE source material

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.

1CVSS vectors
3Timeline events
1ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
7.4CVSS 4.0HighCVSS: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:PGitHub_M

Vulnerability scoring details

Base CVSS 4.0 score

7.4High
CVSS 4.0 vector shape for CVE-2025-27771Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
uptrain-aiuptrain<= 0.7.1Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-74 · source CWE mapping

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.