Refitter: Unrestricted OpenAPI references permit build-host SSRF and file inclusionGHSA-x6w4-f264-3vvr
HIGHFix: christianhelle/refitter#1173GHSA-x6w4-f264-3vvr is a high-severity (CVSS 7.1) CWE-829 vulnerability in Refitter. A fix is available for Refitter — see the affected versions and patch details below.
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.
Exploitation and automatability from CISA’s SSVC triage for GHSA-x6w4-f264-3vvr.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
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 (the refitter dotnet tool, built on NJsonSchema for $ref resolution) fetches remote
http(s) URLs and reads local files (including absolute paths and ../ traversal outside the input
directory), inlining the referenced schema into the generated Refit interface/contracts. Running
refitter <spec> --output Out.cs on a spec whose $ref points at an attacker/internal URL or an
arbitrary local file yields SSRF, remote file inclusion, and local file inclusion. Verified on
Refitter 2.0.0.
Details
$ref: http://attacker-or-internal/evil.json#/...-> build host fetches (SSRF) and inlines the remote schema (RFI); confirmed propertyREMOTE_REFIT_PROP.$ref: /abs/path.json#/...or../../secret.json#/...-> out-of-tree local file read + inlined (LFI); confirmed propertyREFIT_LFI_MARKER. Both absolute and relative traversal work.
No RCE: Refitter emits Refit interfaces with no baseUrl string literal (Refit sets the base address at runtime), enum values use C# verbatim-string doubling, and string defaults are escaped. The chain stops at SSRF + RFI + LFI.
The $ref resolution is performed by Refitter's NJsonSchema dependency, which Refitter ships and
invokes with these unsafe defaults.
PoC
reproduce.sh (+ make_spec.py, listener.py) attached: installs the .NET SDK + Refitter if needed,
confirms LFI (out-of-tree read), SSRF (listener hit during generation), and RFI (remote schema
inlined). Verified on 2.0.0.
Impact
Build-time SSRF (CWE-918) from the developer or CI host, disclosure of arbitrary local files
(CWE-22), and inclusion of untrusted remote content (CWE-829), from running Refitter on an
attacker-controlled or attacker-influenced OpenAPI description. No code execution. Estimated
Medium-High, e.g. [reproduce.sh](https://github.com/user-attachments/files/29395269/reproduce.sh) (the CNA sets the final score).
Suggested fix
Don't resolve remote $refs by default (opt-in + host allowlist); confine local $ref resolution to
the input directory tree (reject absolute paths and ../ escapes). Apply at all nesting levels.
Coordinate with NJsonSchema, where the resolver lives.
maintainer-report.txt
advisory.md
reproduce.sh
maintainer-report.txt
advisory.md
listener.py
make_spec.py
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | Refitter | all versions | 2.1.1dotnet add package Refitter --version 2.1.1 |
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.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x6w4-f264-3vvr is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.
Frequently Asked Questions
Is GHSA-x6w4-f264-3vvr in your dependencies?
Find it across NuGet, including transitive dependencies.