CVE-2026-63346 — Refitter
Fix: christianhelle/refitter@63a19b0CVE-2026-63346 is a Code Injection vulnerability in Refitter. A fix is available for Refitter — see the affected versions and patch details below.
Refitter: C# source injection through OpenAPI header parameter names
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-63346.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
RefitterReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.
Description
Summary
Refitter emits the spec's header parameter name (parameters[].name with in: header) verbatim into a Refit [Header("<name>")] attribute string without escaping
". A crafted value survives Refitter's default OpenAPI validation, breaks out of the attribute and
the enclosing interface + namespace, injects a top-level file class with a [ModuleInitializer]
method, and reopens so the file stays valid. .NET runs [ModuleInitializer] methods at assembly
load, so the attacker's code executes at application startup. Verified on Refitter 2.0.0 / .NET 8.
Notable: the breakout starts from a PARAMETER-LIST position (it closes the params and method first).
The malicious input is a header parameter name. No --skip-validation is required. The query
AliasAs and value sinks (enum, default) are escaped; the gap is in the attribute-string emission.
PoC
reproduce.sh (+ make_spec.py) attached: generates with default validation, compiles into a
console app, runs it (Main does not touch the client), and shows a marker written at assembly load.
Impact
Code execution at assembly load (process startup) in any application that compiles a Refitter client
generated from an attacker-controlled or attacker-influenced OpenAPI description. Estimated Critical, e.g.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N (the CNA sets the final score).
Suggested fix
Escape every spec-derived string before emitting it into a Refit attribute (escape ", \,
reject newlines) and validate characters. We recommend auditing all attribute emissions that embed
spec-derived values, using one shared encoder.
maintainer-report.txt
make_spec.py
reproduce.sh
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | Refitter | all versions | 2.1.2dotnet add package Refitter --version 2.1.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Refitter, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update Refitter to 2.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-63346 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
Frequently Asked Questions
Is CVE-2026-63346 in your dependencies?
Find it across NuGet, including transitive dependencies.