# CVE-2026-119560: OPNsense core through 26.7.8 NTP Configuration Injection via GPS and PPS Fudge Fields


- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 30 Oct 2026
- **Updated:** 30 Oct 2026
- **Also known as:** GHSA-2h55-2m98-rp29

## What is CVE-2026-119560?

CVE-2026-119560 is a medium-severity vulnerability in opnsense core, published on 30 Oct 2026. 

### Official description

OPNsense core through 26.7.8 contains a configuration injection vulnerability that allows authenticated users to append ntpd.conf directives by embedding newlines in the fudge and refid fields. Attackers holding the page-services-ntp-gps or PPS privilege can submit CR/LF characters via services_ntpd_gps.php or services_ntpd_pps.php to inject directives loaded by ntpd running as root.

Weakness: CWE-93 (Improper Neutralization of CRLF Sequences)

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


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

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

## Is CVE-2026-119560 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-119560 is a medium-severity vulnerability in opnsense core, published on 30 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-119560 in the wild and no public exploit code.

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

## Sources

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

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