VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.opennms:opennms: vulnerability history, versions and safety

org.opennms:opennms is a package in the Maven ecosystem. Vulert records 9 vulnerabilities for it across 1 release, from May 2021 to Feb 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
9 vulnerabilities recorded H2 M7
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all org.opennms:opennms vulnerabilities

Vulert verdict on org.opennms:opennms 31.0.3 i

Updated on 23 Oct 2026

Careful: 31.0.3 has 3 known vulnerabilities, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 57/100
  • Security Some issues to review
  • Maintenance Slowing
  • Popularity Niche
  • Community Quiet

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 31.0.3 — affected i
  • Vulnerabilities on record 9 over 1 year · 0 in the last year i
  • Latest disclosure 23 Feb 2023 i
  • Highest CVSS 8.8 i
  • With no published fix 1 i
  • Stars 1,179 i
  • OpenSSF scorecard 2/10 i
  • Last release 45 months ago i
  • Licence non-standard i

Version list, release dates, licence and dependants published by Maven Central, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for org.opennms:opennms, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
31.0.3 13 Jan 2023 M2 non-standard Yes Details →

All 1 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 4
  • 2022 2
  • 2023 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 9 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for org.opennms:opennms

The 5 most severe of 9 vulnerabilities recorded for this package

Search all 9 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-25931: Cross-Site Request Forgery in OpenNMS Horizon 8.8 high 27.1.1 25 May 2021
CVE-2021-3396: OpenNMS Horizon RCE via JEXL2 expression 8.8 high 27.0.4 24 May 2022
CVE-2023-0815: OpenNMS Potential Insertion of Sensitive Information into Log File Vulnerability 6.5 medium 31.0.4 23 Feb 2023
CVE-2023-0846: OpenNMS Horizon and Meridian vulnerable to Cross-site Scripting 6.1 medium 31.0.3 22 Feb 2023
CVE-2023-0867: OpenNMS Meridian and Horizon vulnerable to Cross-site Scripting 6.1 medium 31.0.4 23 Feb 2023

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About org.opennms:opennms

Is org.opennms:opennms safe to use?

Vulert records 9 vulnerabilities for org.opennms:opennms in Maven: 0 critical, 2 high, 7 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is org.opennms:opennms's Vulert package health score?

Vulert scores org.opennms:opennms 57/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of org.opennms:opennms affected?

Yes. 31.0.3, the version you would install today, has 3 known vulnerabilities, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of org.opennms:opennms should I use?

31.0.3 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does org.opennms:opennms have?

9 vulnerabilities are recorded for org.opennms:opennms in the Maven ecosystem: 0 critical, 2 high, 7 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new org.opennms:opennms vulnerabilities disclosed?

0 vulnerabilities were recorded for org.opennms:opennms in the last 12 months, and the oldest entry in this database dates to 25 May 2021. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of org.opennms:opennms are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor org.opennms:opennms for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the org.opennms:opennms version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.