NVD / CVE Program· CNA redhat

CVE-2018-1116: A flaw was found in polkit before version 0.116.

MediumCVSS 4.4 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 17/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 1.1% (FIRST EPSS); higher than 68.5% of all records.
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: policykit-1 (Debian:12) 0.105-21; policykit-1 (Debian:8) 0.105-15~deb8u3; polkit (openSUSE:Tumbleweed) 0.118-7.2.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to policykit-1 (Debian:12) 0.105-21; policykit-1 (Debian:8) 0.105-15~deb8u3; polkit (openSUSE:Tumbleweed) 0.118-7.2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

A flaw was found in polkit before version 0.116. The implementation of the polkit_backend_interactive_authority_check_authorization function in polkitd allows to test for authentication and trigger authentication of unrelated processes owned by other users. This may result in a local DoS and information disclosure.

Broken access control (IDOR)

Published: Jul 10, 2018
Updated: Jun 16, 2026
EPSS: 1.1% · 68th percentile
CWE: CWE-285

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 17 / 40 · 4.4 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 1.1%

CNA vs NVD score

NVD: 4.4
CNA · redhat: 4.7; 0.3 point gap

CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
debian	debian linux	cpe:2.3:o:debian:debian_linux
canonical	ubuntu linux	cpe:2.3:o:canonical:ubuntu_linux
polkit project	polkit	cpe:2.3:a:polkit_project:polkit

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

[UNKNOWN] polkit
- polkit 0.116affected

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

canonical ubuntu linux12.04
debian debian linux8.0
polkit project polkitbefore 0.115

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	policykit-1	before 0.105-21	0.105-21
Debian:8	policykit-1	before 0.105-15~deb8u3	0.105-15~deb8u3
openSUSE:Tumbleweed	polkit	before 0.118-7.2	0.118-7.2
Red Hat:enterprise_linux:7::client	polkit	before 0:0.112-26.el7	0:0.112-26.el7
Red Hat:enterprise_linux:7::client	polkit-debuginfo	before 0:0.112-26.el7	0:0.112-26.el7
Red Hat:enterprise_linux:7::client	polkit-devel	before 0:0.112-26.el7	0:0.112-26.el7
Red Hat:enterprise_linux:7::client	polkit-docs	before 0:0.112-26.el7	0:0.112-26.el7
SUSE:Linux Enterprise Desktop 12 SP3	polkit	before 0.113-5.9.1	0.113-5.9.1
SUSE:Linux Enterprise Module for Basesystem 15	polkit	before 0.114-3.3.1	0.114-3.3.1

Same product

debian: all records

Other highest-scoring records for the same primary product.

CVE-2016-9079A use-after-free vulnerability in SVG Animation has been discovered.KEV
86Now
CVE-2024-44308The issue was addressed with improved checks.KEV
68This week
CVE-2021-25216A second vulnerability in BIND's GSSAPI security policy negotiation can be targeted by a buffer overflow attack
64This week

Published before and after this one in the same product

← EarlierCVE-2018-10852Jun 26, 2018 · The UNIX pipe which sudo uses to contact SSSD and read the available sudo rules from SSSD has too wide permissions, which means that anyone…
30Monitor
← EarlierCVE-2018-13054Jul 2, 2018 · An issue was discovered in Cinnamon 1.9.2 through 3.8.6.
33Monitor
Later →CVE-2018-14040Jul 13, 2018 · In Bootstrap before 4.1.2, XSS is possible in the collapse data-parent attribute.
25Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
debian:policykit-1	0.105-21 · Debian:12	Package registry (OSV)
opensuse:polkit	0.118-7.2 · openSUSE:Tumbleweed	Package registry (OSV)
red hat:polkit	0:0.112-26.el7 · Red Hat:enterprise_linux:7::client	Package registry (OSV)
red hat:polkit-debuginfo	0:0.112-26.el7 · Red Hat:enterprise_linux:7::client	Package registry (OSV)
red hat:polkit-devel	0:0.112-26.el7 · Red Hat:enterprise_linux:7::client	Package registry (OSV)
red hat:polkit-docs	0:0.112-26.el7 · Red Hat:enterprise_linux:7::client	Package registry (OSV)
suse:polkit	0.113-5.9.1 · SUSE:Linux Enterprise Desktop 12 SP3	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.