CVE-2017-18226: The Gentoo net-im/jabberd2 package through 2.6.1 sets the ownership of /var/run/jabber to the jabber account,

Q: How do I fix CVE-2017-18226?

jabberd2: upgrade to newer than 2.6.1. Exact commands for each OS are on this page.

Q: Is CVE-2017-18226 being exploited?

CVE-2017-18226 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-2017-18226 affect?

CVE-2017-18226 affects jabberd2. Severity is medium (CVSS 5.5). The Gentoo net-im/jabberd2 package through 2.6.1 sets the ownership of /var/run/jabber to the jabber account, which might allow local users to kill arbitrary processes by leveraging access to this account for PID file modification before a

Q: How urgent is CVE-2017-18226?

Priority 23/100. No elevated risk signals yet.

Routine

MEDIUM 5.5UPGRADE

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

The Gentoo net-im/jabberd2 package through 2.6.1 sets the ownership of /var/run/jabber to the jabber account, which might allow local users to kill arbitrary processes by leveraging access to this account for PID file modification before a root script executes a "kill -TERM `cat /var/run/jabber/filename.pid`" command.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	5.5 (Medium)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 83%)
CISA exploited list	No
Weakness	CWE-732
Published	2018-03-12
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: jabberd2

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

Am I affected?

Timeline

2018-03-12 04:29 UTCPublished CVE record published
2026-06-17 01:12 UTCUpdated Record last modified

jabberd2 jabberd2 UPGRADE

Affected: <= 2.6.1

Fixed in: newer than 2.6.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy jabberd2 || rpm -q jabberd2 || jabberd2 --version

2. UPGRADE to newer than 2.6.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade jabberd2

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade jabberd2

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-2017-18226?

jabberd2: upgrade to newer than 2.6.1. Exact commands for each OS are on this page.

Is CVE-2017-18226 being exploited?

CVE-2017-18226 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-2017-18226 affect?

CVE-2017-18226 affects jabberd2. Severity is medium (CVSS 5.5). The Gentoo net-im/jabberd2 package through 2.6.1 sets the ownership of /var/run/jabber to the jabber account, which might allow local users to kill arbitrary processes by leveraging access to this account for PID file modification before a

How urgent is CVE-2017-18226?

Priority 23/100. No elevated risk signals yet.

Related CVEs

CVE-2017-18225 HIGH 7.8 UPGRADE The Gentoo net-im/jabberd2 package through 2.6.1 installs jabberd, jabberd2-c2s, jabberd2-router, jabberd2-s2s
CVE-2017-10807 CRITICAL 9.8 UPGRADE JabberD 2.x (aka jabberd2) before 2.6.1 allows anyone to authenticate using SASL ANONYMOUS, even when the sasl

References

← Back to latest CVEs