CVE-2025-27621: CWE-287: Improper Authentication in uptrain-ai uptrain
UpTrain versions 0.7.1 and earlier contain an improper authentication vulnerability where a default user is created with a static username that doubles as the default API key. The backend also has an open CORS policy, allowing any website to make authenticated cross-origin requests using this default API key. This can enable arbitrary websites to perform privileged operations as the default user. No patches are currently available for this issue.
AI Analysis
Technical Summary
UpTrain, an open-source platform for evaluating generative AI applications, has an authentication flaw in version 0.7.1 and prior. The backend creates a default user with a static username that is also used as the default API key. Combined with an open Cross-Origin Resource Sharing (CORS) policy, this allows any external website to send authenticated requests by including the default API key in the 'uptrain-access-token' header. This improper authentication (CWE-287) can lead to unauthorized privileged operations on the UpTrain instance, effectively impersonating the default logged-in user. As of the publication date, no official fix or patch is available.
Potential Impact
An attacker controlling a website can exploit the default static API key and open CORS policy to perform privileged actions on the UpTrain backend without authorization. This compromises the integrity and security of the UpTrain instance by allowing unauthorized operations as the default user. The vulnerability has a high severity rating (CVSS 7.7) due to its network accessibility, lack of authentication barriers, and potential for significant impact on the affected system.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, users should consider restricting access to the UpTrain backend, disabling or limiting CORS policies, and changing or removing the default static API key if possible. Monitoring for unusual activity and isolating the UpTrain instance from untrusted networks may reduce risk.
CVE-2025-27621: CWE-287: Improper Authentication in uptrain-ai uptrain
Description
UpTrain versions 0.7.1 and earlier contain an improper authentication vulnerability where a default user is created with a static username that doubles as the default API key. The backend also has an open CORS policy, allowing any website to make authenticated cross-origin requests using this default API key. This can enable arbitrary websites to perform privileged operations as the default user. No patches are currently available for this issue.
CVSS v4.0
Score 7.7high
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
UpTrain, an open-source platform for evaluating generative AI applications, has an authentication flaw in version 0.7.1 and prior. The backend creates a default user with a static username that is also used as the default API key. Combined with an open Cross-Origin Resource Sharing (CORS) policy, this allows any external website to send authenticated requests by including the default API key in the 'uptrain-access-token' header. This improper authentication (CWE-287) can lead to unauthorized privileged operations on the UpTrain instance, effectively impersonating the default logged-in user. As of the publication date, no official fix or patch is available.
Potential Impact
An attacker controlling a website can exploit the default static API key and open CORS policy to perform privileged actions on the UpTrain backend without authorization. This compromises the integrity and security of the UpTrain instance by allowing unauthorized operations as the default user. The vulnerability has a high severity rating (CVSS 7.7) due to its network accessibility, lack of authentication barriers, and potential for significant impact on the affected system.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, users should consider restricting access to the UpTrain backend, disabling or limiting CORS policies, and changing or removing the default static API key if possible. Monitoring for unusual activity and isolating the UpTrain instance from untrusted networks may reduce risk.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2025-03-03T15:10:34.080Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a83368ebf8831d53930a3cd
Added to database: 08/17/2026, 16:27:58 UTC
Last enriched: 08/17/2026, 16:43:19 UTC
Last updated: 08/17/2026, 22:32:42 UTC
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.