# CVE-2025-29705: Missing authorization in n/a

> An attacker can access projects without permission due to missing access controls in the code-gen library.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Apr 2025
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-h7mj-68q6-fwp5

## What is CVE-2025-29705?

CVE-2025-29705 is a medium-severity missing authorization vulnerability in n/a, published on 15 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

code-gen <=2.0.6 is vulnerable to Incorrect Access Control. The project does not have permission control allowing anyone to access such projects.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2025-29705?

It affects 1 product.


Products: Tanghc Code-Gen.

## How do I fix CVE-2025-29705?

No fix has been published for CVE-2025-29705 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-29705 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-29705 exists.

Public exploit code:

- CVE-2025-29705 (github_poc): https://github.com/yxzrw/CVE-2025-29705

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-29705 and fix it if it is affected.

What it is: CVE-2025-29705 is a medium-severity missing authorization vulnerability in n/a, published on 15 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-29705 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-29705/ (Markdown: https://insights.sbomify.com/CVE-2025-29705/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-29705
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-29705
- OSV: https://osv.dev/vulnerability/CVE-2025-29705

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-29705/
Summaries are generated and may contain mistakes; the official description above is the record.