Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify target CSGHub instance and private repo
-
DeliveryCraft resolve request with percent-encoded current_user in path
-
ExploitPortal forwards request with server API key
-
ExecutionAuthorization check bypassed (IDOR)
-
ImpactPrivate repository file contents returned to attacker
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
|
| Exploitation Conditions | No special conditions beyond reachability - remote, unauthenticated exploitation against default configurations of OpenCSG CSGHub up to and including v2.6.0-ce, via the public (unauthenticated) file resolve route. The specific trigger is injecting a percent-encoded current_user parameter into the requested file path, which the portal forwards to the backend server API using its own server API key, causing the authorization check to be bypassed. Limiting factors: the target must be a reachable CSGHub portal instance and the attacker must know or enumerate the path of a private model, code, or space repository; impact is confined to reading files (confidentiality only - no write or availability effect). No fixed version is identified in the available sources, so the primary limiting factor on remediation is the absence of a confirmed patched build in the evidence. |
| Impact | This is an unauthenticated information-disclosure flaw (CWE-639, IDOR / authorization bypass through a user-controlled key) in OpenCSG CSGHub's file resolve route. The supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N) is internally consistent with the description: fully remote, low complexity, no privileges, no user interaction, with high confidentiality impact and no integrity or availability impact - a clean read-only exposure of private repository contents. The signals mostly agree: VulnCheck has published an advisory and there is a public HackMD technical write-up, and the vuln.today decision label is 'this_week', which places it as a near-term priority rather than an emergency. However, several escalation signals are ABSENT from the input: there is no EPSS probability provided, no CISA KEV listing, and no confirmation of weaponized exploit code - so active, widespread exploitation cannot be asserted. Net assessment: a genuinely exploitable, low-friction confidentiality bug that merits prompt patching given its trivial attack preconditions, but its real-world priority is tempered by the product's limited deployment footprint and the absence of KEV/EPSS data confirming mass exploitation. The 8.7 input score reflects ease of attack and high confidentiality loss; it is not inflated, but neither is there evidence of in-the-wild abuse. |
| Exploit ScenarioDerived | A remote attacker with no account browses a CSGHub instance and targets a private model, code, or space repository. They craft a file-resolve request injecting a percent-encoded current_user parameter into the file path; the portal forwards the request to its server API using its own privileged server API key, bypassing the per-user authorization check and returning the private file contents. A public PoC reference (HackMD write-up and VulnCheck advisory) describes the technique, but it is not verified as working exploit code. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 02, 2026
OpenCSG CSGHub through v2.6.0-ce allows unauthenticated remote attackers to read files from private model, code, and space repositories by abusing the public file resolve route. The flaw is an authorization bypass (CWE-639) in which a percent-encoded current_user parameter injected into the file path is forwarded by the portal to the backend with the portal's server API key, causing the backend authorization check to trust the attacker-controlled identity. Published severity is CVSS 8.7 (CVSS 4.0), with assessed impact limited to high confidentiality loss; no CISA KEV entry is provided, a public technical write-up exists but working exploit code is not confirmed, and no fixed version is identified in the supplied sources.
RemediationAI
No vendor-released patch or fixed version is identified in the supplied sources; track the GitHub issue (https://github.com/OpenCSGs/csghub/issues/1586) and VulnCheck advisory (https://www.vulncheck.com/advisories/opencsg-csghub-through-2.6.0-ce-unauthenticated-private-repository-file-read-via-resolve-route) for a patched release. Until a fix is available, gate or disable the unauthenticated file resolve route at the reverse proxy or WAF so that all file-resolution requests require authentication; the trade-off is that anonymous/public repository browsing and integrations that rely on that route may break. Alternatively, place the entire CSGHub portal behind an authenticated proxy or VPN restricted to trusted users, which reduces exposure but removes public access. Review the route registration referenced in router.go L302-L303 to identify the exact path in your deployment, and monitor access logs for file-resolution requests containing percent-encoded current_user parameters or for private-repository file reads from unauthenticated clients.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
CSGHub is an open-source platform for hosting and serving model, dataset, code, and space repositories; the affected component is its Go-based portal and backend API. The route is registered without authentication in router.go (L302-L303), handled by the frontend resolve handler in resolve.go (L138-L151), and forwarded to backend download code in download.go (L10-L41), with identity handling in authenticator.go (L210-L226). The root cause is CWE-639: the backend derives the effective user from a user-controlled key (current_user) rather than from an authenticated session, and because the portal forwards the request using its server API key, the backend treats the call as trusted. The supplied evidence specifically identifies percent-encoded current_user injection into the requested file path as the trigger; other mechanisms are not described. The CPE cpe:2.3:a:opencsg:csghub:*:*:*:*:*:*:*:* is broad, while the advisory scopes affected releases to through v2.6.0-ce. The published CVSS 4.0 vector and the independent CVSS 3.1 assessment both indicate network reachability, no privileges, no user interaction, and confidentiality-only impact.
Know when Csghub gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Remote unauthenticated resolve route (AV:N/AC:L/PR:N/UI:N) yields high confidentiality loss of private repo files; no integrity or availability impact and no scope change.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
OpenCSG CSGHub through v2.6.0-ce contains an authorization bypass vulnerability in the unauthenticated file resolve route that allows remote attackers to read private repository files. Attackers can inject a percent-encoded current_user parameter into the file path, which the portal forwards with its server API key, to read files in private model, code or space repositories.
Executive ViewAI
CSGHub, an open-source platform for hosting private AI models and datasets, contains an authorization bypass that allows unauthenticated attackers to read sensitive files from private repositories. This puts proprietary AI models, source code, and related intellectual property at risk across any organization using affected versions (through v2.6.0-ce). Leadership should prioritize mitigation because the exposed assets are core to competitive advantage and may contain regulated data.
No vendor patch is available. Interim mitigations include restricting network access to the CSGHub portal, disabling the public file resolve route if feasible, implementing WAF rules to block malicious percent-encoded parameters, and enforcing strict authorization checks at the backend independent of portal-supplied identity.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
EUVD-2026-115235
GHSA-p8qg-p5c7-m59c
NVD
CVE.org
EPSS
Exploit-DB