Refitter is a tool for generating a C# REST API client using the Refit library. Prior to 2.1.2, the header parameter name in `parameters[].name` with `in: header` is emitted verbatim into a Refit `[Header("<name>")]` attribute string without escaping quotation marks. An attacker-influenced OpenAPI description can pass default validation without `--skip-validation` and break out from the parameter-list position by closing the parameter and method syntax, attribute, interface, and namespace. The generated file can remain valid C# while containing a top-level file class with a `[ModuleInitializer]` method, which executes attacker code when the compiled assembly is loaded at application startup, even if the client is never called. Query `AliasAs` and enum/default value sinks are escaped; this flaw is in header-name attribute-string emission. The behavior was verified with Refitter 2.0.0 and .NET 8. This issue is fixed in version 2.1.2.
0.6%(up from 0.4% a week ago) estimated probability of exploitation activity in the next 30 days; 48th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-94Improper Control of Generation of Code (Code Injection) CWE-116Improper Encoding or Escaping of Output
Show the promptExplain CVE-2026-63346 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-63346?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-63346?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-63346 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.
googlesky/CVE-2026-63346Harbor Check: matches CVE0 stars, Python, created Refitter <2.1.2: header parameter name emitted verbatim into [Header(...)] attribute — crafted name injects a [ModuleInitializer] file clas…
Attack patterns (CAPEC)
CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
CAPEC-77 Manipulating User-Controlled Variables Likelihood: High · Severity: Very High
CAPEC-242 Code Injection Likelihood: High · Severity: High
CAPEC-73 User-Controlled Filename Likelihood: High · Severity: High
CAPEC-81 Web Server Logs Tampering Likelihood: Medium · Severity: High
CAPEC-85 AJAX Footprinting Likelihood: High · Severity: Low
CAPEC-104 Cross Zone Scripting Likelihood: Medium · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.