# CVE-2026-119027: oapi-codegen 2.5.0 before 2.8.1 Code Injection via servers[].x-go-name Extension


- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-prxp-239m-mh9f

## What is CVE-2026-119027?

CVE-2026-119027 is a high-severity vulnerability in oapi-codegen, published on 29 Oct 2026. 

### Official description

oapi-codegen 2.5.0 before 2.8.1 contains a code injection vulnerability that allows attackers to inject Go code by supplying a crafted servers[].x-go-name value emitted unescaped by the server-urls template. Attackers who control an OpenAPI document can define an injected func init() that executes when the victim builds and imports the generated package.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-119027?


## How do I fix CVE-2026-119027?

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

## Is CVE-2026-119027 being exploited?

There is no known exploitation of CVE-2026-119027 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119027 and fix it if it is affected.

What it is: CVE-2026-119027 is a high-severity vulnerability in oapi-codegen, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-119027 in the wild and no public exploit code.

Affected product: oapi-codegen. 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-2026-119027/ (Markdown: https://insights.sbomify.com/CVE-2026-119027/index.md)
```

## Sources

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

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