# CVE-2016-0726: Hardcoded credentials in n/a

> Remote attackers can gain administrator access to Nagios by using the default hardcoded credentials provided in the Fedora package.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rg2g-95pj-mc2p

## What is CVE-2016-0726?

CVE-2016-0726 is a critical vulnerability in n/a, published on 6 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Fedora Nagios package uses "nagiosadmin" as the default password for the "nagiosadmin" administrator account, which makes it easier for remote attackers to obtain access by leveraging knowledge of the credentials.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2016-0726?

It affects 1 product.


Products: Nagios Nagios.

## How do I fix CVE-2016-0726?

Change a configuration setting.

## Is CVE-2016-0726 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-1959](https://insights.sbomify.com/CVE-2002-1959/): Command injection in n/a (critical 10.0)
- [CVE-2008-7313](https://insights.sbomify.com/CVE-2008-7313/): Command injection in n/a (critical 9.8)
- [CVE-2014-5009](https://insights.sbomify.com/CVE-2014-5009/): Command injection in n/a (critical 9.8)
- [CVE-2016-9565](https://insights.sbomify.com/CVE-2016-9565/): Path traversal in n/a (critical 9.8)
- [CVE-2020-6585](https://insights.sbomify.com/CVE-2020-6585/): Nagios Log Server 2.1.3 has CSRF. (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-0726 and fix it if it is affected.

What it is: CVE-2016-0726 is a critical vulnerability in n/a, published on 6 Jun 2017. 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-2016-0726 in the wild and no public exploit code.

Affected product: n/a. 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-2016-0726/ (Markdown: https://insights.sbomify.com/CVE-2016-0726/index.md)
```

## Sources

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

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