CVE-2016-15018: A vulnerability was found in krail-jpa up to 0.9.1

Q: How do I fix CVE-2016-15018?

krail-jpa: upgrade to 0.9.2. Exact commands for each OS are on this page.

Q: Is CVE-2016-15018 being exploited?

CVE-2016-15018 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2016-15018 affect?

CVE-2016-15018 affects krail-jpa. Severity is medium (CVSS 5.5). A vulnerability was found in krail-jpa up to 0.9.1. It has been classified as critical. This affects an unknown part. The manipulation leads to sql injection. Upgrading to version 0.9.2 is able to address this issue. The identifier of the p

Q: How urgent is CVE-2016-15018?

Priority 38/100. Public exploit reference

Routine

MEDIUM 5.5UPGRADE

CVE-2016-15018 is a medium-severity flaw (CVSS 5.5) affecting krail-jpa. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A vulnerability was found in krail-jpa up to 0.9.1. It has been classified as critical. This affects an unknown part. The manipulation leads to sql injection. Upgrading to version 0.9.2 is able to address this issue. The identifier of the patch is c1e848665492e21ef6cc9be443205e36b9a1f6be. It is recommended to upgrade the affected component. The identifier VDB-218373 was assigned to this vulnerability.

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	5.5 (Medium)
Attack vector	Adjacent network
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.8% (top 44%)
CISA exploited list	No
Weakness	CWE-89
Published	2023-01-15
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: krail-jpa project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2023-01-15 19:15 UTCPublished CVE record published
2026-06-17 00:41 UTCUpdated Record last modified

krail-jpa project krail-jpa UPGRADE

Affected: < 0.9.2

Fixed in: 0.9.2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy krail-jpa || rpm -q krail-jpa || krail-jpa --version

2. UPGRADE to 0.9.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade krail-jpa

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade krail-jpa

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2016-15018?

krail-jpa: upgrade to 0.9.2. Exact commands for each OS are on this page.

Is CVE-2016-15018 being exploited?

CVE-2016-15018 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2016-15018 affect?

CVE-2016-15018 affects krail-jpa. Severity is medium (CVSS 5.5). A vulnerability was found in krail-jpa up to 0.9.1. It has been classified as critical. This affects an unknown part. The manipulation leads to sql injection. Upgrading to version 0.9.2 is able to address this issue. The identifier of the p

How urgent is CVE-2016-15018?

Priority 38/100. Public exploit reference

References

← Back to latest CVEs