Exposure of Sensitive Information to an Unauthorized Actor in LibreNMS

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2019-10667: 1.22% estimated exploitation activity in the next 30 days; percentile 68.68 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

An issue was discovered in LibreNMS through 1.47. Information disclosure can occur: an attacker can fingerprint the exact code version installed and disclose local file paths.

Published by the source

11 Oct 2019, 18:43 UTC

Last modified by the source

1 Feb 2023, 05:02 UTC

Source last checked

26 Oct 2026, 14:01 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-f4hh-xxqh-wgpq

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2019-10667

Advisory: Exposure of Sensitive Information to an Unauthorized Actor in LibreNMS
IDs: CVE-2019-10667, GHSA-f4hh-xxqh-wgpq
Record: https://patchnext.com/advisories/cve-2019-10667 (revision 1, source checked 26 Oct 2026, 14:01 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: librenms/librenms 1.50.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist librenms/librenms: affected < 1.50.1; fixed in 1.50.1

## Suggested inspection (read-only)
- Packagist librenms/librenms: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on librenms/librenms.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-f4hh-xxqh-wgpq (GitHub-reviewed advisory GHSA-f4hh-xxqh-wgpq lists affected ranges: Packagist librenms/librenms >=0 <1.50.1)

Commands are suggestions: review each one before running it.