# CVE-2026-54918: Server-side request forgery in devicetype-library

> Attackers can manipulate CI test configurations to trigger SSRF and bypass validation checks in the NetBox Device Type Library.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-8cfp-3c4q-xr6x

## What is CVE-2026-54918?

CVE-2026-54918 is a medium-severity server-side request forgery vulnerability in netbox-community devicetype-library, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

NetBox Device Type Library is a collection of community-sourced device type definitions for import into NetBox. In the affected repository revisions, NETBOX_DT_LIBRARY_URL in tests/test_configuration.py is a free-form tracked constant that an unauthenticated pull-request author can change before the validation test harness runs. During pytest collection, tests/definitions_test.py passes the value to Repo.clone_from and create_remote("upstream").fetch(), causing blind Git smart-HTTP requests to an attacker-selected host or loading attacker-controlled tests/known-*.json validation caches. The blind request cannot set arbitrary metadata-service headers or return response bodies, and this path does not execute remote Git hooks, but substituted known data can bypass slug, module, and rack uniqueness validation. This vulnerability is fixed in commit 8980c690097e92f5028c7e6df402b327d827ecd5.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-829 (Inclusion of Functionality from Untrusted Control Sphere), CWE-15 (External Control of System or Configuration Setting)

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


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

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

## Is CVE-2026-54918 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54918 is a medium-severity server-side request forgery vulnerability in netbox-community devicetype-library, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-54918 in the wild and no public exploit code.

Affected product: netbox-community devicetype-library. 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-54918/ (Markdown: https://insights.sbomify.com/CVE-2026-54918/index.md)
```

## Sources

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

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