CVE-2018-6118
A double-eviction in the Incognito mode cache that lead to a user-after-free in cache in Google...
A double-eviction in the Incognito mode cache that lead to a user-after-free in cache in Google Chrome prior to 66.0.3359.139 allowed a remote attacker who had compromised the renderer process to execute arbitrary code via a crafted HTML page.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- Required
What an attacker can affect
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Exploit likelihood
What each source reports
NVD Score used
8.8
A double-eviction in the Incognito mode cache that lead to a user-after-free in cache in Google Chrome prior to 66.0.3359.139 allowed a remote attacker who had compromised the renderer process to execute arbitrary code via a crafted HTML page.
- Record
CVE-2018-6118- CVSS 3.0
- 8.8 High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H - CVSS 2.0
- 6.8 Medium
AV:N/AC:M/Au:N/C:P/I:P/A:P - Weakness
- CWE-416
- Updated
- 2026-11-02
CVE List No score
A double-eviction in the Incognito mode cache that lead to a user-after-free in cache in Google Chrome prior to 66.0.3359.139 allowed a remote attacker who had compromised the renderer process to execute arbitrary code via a crafted HTML page.
- Record
CVE-2018-6118- Updated
- 2026-11-02
EUVDEUVD-2018-17881 No score
A double-eviction in the Incognito mode cache that lead to a user-after-free in cache in Google Chrome prior to 66.0.3359.139 allowed a remote attacker who had compromised the renderer process to execute arbitrary code via a crafted HTML page.
- Record
EUVD-2018-17881- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-g93q-r5hj-4m44
8.8
A double-eviction in the Incognito mode cache that lead to a user-after-free in cache in Google...
A double-eviction in the Incognito mode cache that lead to a user-after-free in cache in Google Chrome prior to 66.0.3359.139 allowed a remote attacker who had compromised the renderer process to execute arbitrary code via a crafted HTML page.
- Record
GHSA-g93q-r5hj-4m44- CVSS 3.0
- 8.8 High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H - Weakness
- CWE-416
- Updated
- 2026-11-02
OSVRHSA-2018:1321
9.6
Red Hat Security Advisory: chromium-browser security update
- Record
RHSA-2018:1321- CVSS 3.0
- 9.6 Critical
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H - Updated
- 2026-11-02
OSVUBUNTU-CVE-2018-6118
8.8
A double-eviction in the Incognito mode cache that lead to a user-after-free in cache in Google Chrome prior to 66.0.3359.139 allowed a remote attacker who had compromised the renderer process to execute arbitrary code via a crafted HTML page.
- Record
UBUNTU-CVE-2018-6118- CVSS 3.0
- 8.8 High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
Show 5 moreShow less
OSVMGASA-2018-0268 No score
Updated chromium-browser-stable packages fix security vulnerabilities
Chromium-browser 67.0.3396.62 fixes security issues:
Multiple flaws were found in the way Chromium 64.0.3282.140 processes various types of web content, where loading a web page containing malicious content could cause Chromium to crash, execute arbitrary code, or disclose sensitive information. (CVE-2017-11215, CVE-2017-11225, CVE-2018-6056, CVE-2018-6057, CVE-2018-6060, CVE-2018-6061, CVE-2018-6062, CVE-2018-6063, CVE-2018-6064, CVE-2018-6065, CVE-2018-6066, CVE-2018-6067, CVE-2018-6068, CVE-2018-6069, CVE-2018-6070, CVE-2018-6071, CVE-2018-6072, CVE-2018-6073, CVE-2018-6074, CVE-2018-6075, CVE-2018-6076, CVE-2018-6077, CVE-2018-6078, CVE-2018-6079, CVE-2018-6080, CVE-2018-6081, CVE-2018-6082, CVE-2018-6083, CVE-2018-6084, CVE-2018-6085, CVE-2018-6086, CVE-2018-6087, CVE-2018-6088, CVE-2018-6089, CVE-2018-6090, CVE-2018-6091, CVE-2018-6092, CVE-2018-6093, CVE-2018-6094, CVE-2018-6095, CVE-2018-6096, CVE-2018-6097, CVE-2018-6098, CVE-2018-6099, CVE-2018-6100, CVE-2018-6101, CVE-2018-6102, CVE-2018-6103, CVE-2018-6104, CVE-2018-6105, CVE-2018-6106, CVE-2018-6107, CVE-2018-6108, CVE-2018-6109, CVE-2018-6110, CVE-2018-6111, CVE-2018-6112, CVE-2018-6113, CVE-2018-6114, CVE-2018-6115, CVE-2018-6116, CVE-2018-6117, CVE-2018-6118, CVE-2018-6120, CVE-2018-6121, CVE-2018-6122, CVE-2018-6123, CVE-2018-6124, CVE-2018-6126, CVE-2018-6127, CVE-2018-6128, CVE-2018-6129, CVE-2018-6130, CVE-2018-6131, CVE-2018-6132, CVE-2018-6133, CVE-2018-6134, CVE-2018-6135, CVE-2018-6136, CVE-2018-6137, CVE-2018-6138, CVE-2018-6139, CVE-2018-6140, CVE-2018-6141, CVE-2018-6142, CVE-2018-6143, CVE-2018-6144, CVE-2018-6145, CVE-2018-6147)
- Record
MGASA-2018-0268- Updated
- 2026-11-02
OSVopenSUSE-SU-2018:1175-1 No score
Security update for Chromium
This update for Chromium to version 66.0.3359.181 fixes the following issues:
- CVE-2018-6118: Use after free in Media Cache (bsc#1091288)
- CVE-2018-6085: Use after free in Disk Cache
- CVE-2018-6086: Use after free in Disk Cache
- CVE-2018-6087: Use after free in WebAssembly
- CVE-2018-6088: Use after free in PDFium
- CVE-2018-6089: Same origin policy bypass in Service Worker
- CVE-2018-6090: Heap buffer overflow in Skia
- CVE-2018-6091: Incorrect handling of plug-ins by Service Worker
- CVE-2018-6092: Integer overflow in WebAssembly
- CVE-2018-6093: Same origin bypass in Service Worker
- CVE-2018-6094: Exploit hardening regression in Oilpan
- CVE-2018-6095: Lack of meaningful user interaction requirement before file upload
- CVE-2018-6096: Fullscreen UI spoof
- CVE-2018-6097: Fullscreen UI spoof
- CVE-2018-6098: URL spoof in Omnibox
- CVE-2018-6099: CORS bypass in ServiceWorker
- CVE-2018-6100: URL spoof in Omnibox
- CVE-2018-6101: Insufficient protection of remote debugging prototol in DevTools
- CVE-2018-6102: URL spoof in Omnibox
- CVE-2018-6103: UI spoof in Permissions
- CVE-2018-6104: URL spoof in Omnibox
- CVE-2018-6105: URL spoof in Omnibox
- CVE-2018-6106: Incorrect handling of promises in V8
- CVE-2018-6107: URL spoof in Omnibox
- CVE-2018-6108: URL spoof in Omnibox
- CVE-2018-6109: Incorrect handling of files by FileAPI
- CVE-2018-6110: Incorrect handling of plaintext files via file://
- CVE-2018-6111: Heap-use-after-free in DevTools
- CVE-2018-6112: Incorrect URL handling in DevTools
- CVE-2018-6113: URL spoof in Navigation
- CVE-2018-6114: CSP bypass
- CVE-2018-6115: SmartScreen bypass in downloads
- CVE-2018-6116: Incorrect low memory handling in WebAssembly
- CVE-2018-6117: Confusing autofill settings
- CVE-2017-11215: Use after free in Flash
- CVE-2017-11225: Use after free in Flash
- CVE-2018-6060: Use after free in Blink
- CVE-2018-6061: Race condition in V8
- CVE-2018-6062: Heap buffer overflow in Skia
- CVE-2018-6057: Incorrect permissions on shared memory
- CVE-2018-6063: Incorrect permissions on shared memory
- CVE-2018-6064: Type confusion in V8
- CVE-2018-6065: Integer overflow in V8
- CVE-2018-6066: Same Origin Bypass via canvas
- CVE-2018-6067: Buffer overflow in Skia
- CVE-2018-6068: Object lifecycle issues in Chrome Custom Tab
- CVE-2018-6069: Stack buffer overflow in Skia
- CVE-2018-6070: CSP bypass through extensions
- CVE-2018-6071: Heap bufffer overflow in Skia
- CVE-2018-6072: Integer overflow in PDFium
- CVE-2018-6073: Heap bufffer overflow in WebGL
- CVE-2018-6074: Mark-of-the-Web bypass
- CVE-2018-6075: Overly permissive cross origin downloads
- CVE-2018-6076: Incorrect handling of URL fragment identifiers in Blink
- CVE-2018-6077: Timing attack using SVG filters
- CVE-2018-6078: URL Spoof in OmniBox
- CVE-2018-6079: Information disclosure via texture data in WebGL
- CVE-2018-6080: Information disclosure in IPC call
- CVE-2018-6081: XSS in interstitials
- CVE-2018-6082: Circumvention of port blocking
- CVE-2018-6083: Incorrect processing of AppManifests
- CVE-2018-6121: Privilege Escalation in extensions
- CVE-2018-6122: Type confusion in V8
- CVE-2018-6120: Heap buffer overflow in PDFium
- bsc#1086124: Various fixes from internal audits, fuzzing and other initiatives
This update also supports mitigation against the Spectre vulnerabilities:
'Strict site isolation' is disabled for most users and can be turned on via: chrome://flags/#enable-site-per-process
This feature is undergoing a small percentage trial. Out out of the trial is possible via: chrome://flags/#site-isolation-trial-opt-out
The following tracked packaging bug were fixed:
- Chromium could not be installed from SUSE PackageHub 12 without having the SDK enabled (bsc#1070421)
- Chromium could not be installed when libminizip1 was not available (bsc#1093031)
- Record
openSUSE-SU-2018:1175-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2018:1437-1 No score
Security update for Chromium
This update for Chromium to version 66.0.3359.181 fixes the following issues:
- CVE-2018-6118: Use after free in Media Cache (bsc#1091288)
- CVE-2018-6085: Use after free in Disk Cache
- CVE-2018-6086: Use after free in Disk Cache
- CVE-2018-6087: Use after free in WebAssembly
- CVE-2018-6088: Use after free in PDFium
- CVE-2018-6089: Same origin policy bypass in Service Worker
- CVE-2018-6090: Heap buffer overflow in Skia
- CVE-2018-6091: Incorrect handling of plug-ins by Service Worker
- CVE-2018-6092: Integer overflow in WebAssembly
- CVE-2018-6093: Same origin bypass in Service Worker
- CVE-2018-6094: Exploit hardening regression in Oilpan
- CVE-2018-6095: Lack of meaningful user interaction requirement before file upload
- CVE-2018-6096: Fullscreen UI spoof
- CVE-2018-6097: Fullscreen UI spoof
- CVE-2018-6098: URL spoof in Omnibox
- CVE-2018-6099: CORS bypass in ServiceWorker
- CVE-2018-6100: URL spoof in Omnibox
- CVE-2018-6101: Insufficient protection of remote debugging prototol in DevTools
- CVE-2018-6102: URL spoof in Omnibox
- CVE-2018-6103: UI spoof in Permissions
- CVE-2018-6104: URL spoof in Omnibox
- CVE-2018-6105: URL spoof in Omnibox
- CVE-2018-6106: Incorrect handling of promises in V8
- CVE-2018-6107: URL spoof in Omnibox
- CVE-2018-6108: URL spoof in Omnibox
- CVE-2018-6109: Incorrect handling of files by FileAPI
- CVE-2018-6110: Incorrect handling of plaintext files via file://
- CVE-2018-6111: Heap-use-after-free in DevTools
- CVE-2018-6112: Incorrect URL handling in DevTools
- CVE-2018-6113: URL spoof in Navigation
- CVE-2018-6114: CSP bypass
- CVE-2018-6115: SmartScreen bypass in downloads
- CVE-2018-6116: Incorrect low memory handling in WebAssembly
- CVE-2018-6117: Confusing autofill settings
- CVE-2017-11215: Use after free in Flash
- CVE-2017-11225: Use after free in Flash
- CVE-2018-6060: Use after free in Blink
- CVE-2018-6061: Race condition in V8
- CVE-2018-6062: Heap buffer overflow in Skia
- CVE-2018-6057: Incorrect permissions on shared memory
- CVE-2018-6063: Incorrect permissions on shared memory
- CVE-2018-6064: Type confusion in V8
- CVE-2018-6065: Integer overflow in V8
- CVE-2018-6066: Same Origin Bypass via canvas
- CVE-2018-6067: Buffer overflow in Skia
- CVE-2018-6068: Object lifecycle issues in Chrome Custom Tab
- CVE-2018-6069: Stack buffer overflow in Skia
- CVE-2018-6070: CSP bypass through extensions
- CVE-2018-6071: Heap bufffer overflow in Skia
- CVE-2018-6072: Integer overflow in PDFium
- CVE-2018-6073: Heap bufffer overflow in WebGL
- CVE-2018-6074: Mark-of-the-Web bypass
- CVE-2018-6075: Overly permissive cross origin downloads
- CVE-2018-6076: Incorrect handling of URL fragment identifiers in Blink
- CVE-2018-6077: Timing attack using SVG filters
- CVE-2018-6078: URL Spoof in OmniBox
- CVE-2018-6079: Information disclosure via texture data in WebGL
- CVE-2018-6080: Information disclosure in IPC call
- CVE-2018-6081: XSS in interstitials
- CVE-2018-6082: Circumvention of port blocking
- CVE-2018-6083: Incorrect processing of AppManifests
- CVE-2018-6121: Privilege Escalation in extensions
- CVE-2018-6122: Type confusion in V8
- CVE-2018-6120: Heap buffer overflow in PDFium
- bsc#1086124: Various fixes from internal audits, fuzzing and other initiatives
This update also supports mitigation against the Spectre vulnerabilities:
'Strict site isolation' is disabled for most users and can be turned on via: chrome://flags/#enable-site-per-process
This feature is undergoing a small percentage trial. Out out of the trial is possible via: chrome://flags/#site-isolation-trial-opt-out
The following tracked packaging bug were fixed:
- Chromium could not be installed from SUSE PackageHub 12 without having the SDK enabled (bsc#1070421)
- Chromium could not be installed when libminizip1 was not available (bsc#1093031)
- Record
openSUSE-SU-2018:1437-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2024:10681-1 No score
chromedriver-93.0.4577.82-1.1 on GA media
These are all security issues fixed in the chromedriver-93.0.4577.82-1.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2024:10681-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2024:12948-1 No score
ungoogled-chromium-113.0.5672.92-1.1 on GA media
These are all security issues fixed in the ungoogled-chromium-113.0.5672.92-1.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2024:12948-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
chromium-browserDebian:9 |
before 67.0.3396.87-1~deb9u1, plus listed versions 59.0.3071.104-159.0.3071.86-160.0.3112.72-160.0.3112.78-160.0.3112.78-1~deb9u1 Show 36 moreShow less61.0.3163.100-161.0.3163.100-1~deb9u161.0.3163.100-262.0.3202.75-162.0.3202.75-1~deb9u162.0.3202.89-162.0.3202.89-1~deb9u163.0.3239.30-163.0.3239.40-163.0.3239.84-163.0.3239.84-1~deb9u164.0.3282.119-164.0.3282.119-1~deb9u164.0.3282.119-265.0.3325.146-165.0.3325.146-265.0.3325.146-365.0.3325.146-465.0.3325.73-165.0.3325.74-166.0.3359.117-166.0.3359.117-1~deb9u166.0.3359.139-166.0.3359.181-166.0.3359.22-166.0.3359.22-266.0.3359.22-366.0.3359.26-166.0.3359.26-267.0.3396.48-167.0.3396.56-167.0.3396.57-167.0.3396.62-167.0.3396.62-267.0.3396.79-167.0.3396.79-2 |
67.0.3396.87-1~deb9u1 |
chromium-browser-stableMageia:6 |
before 67.0.3396.62-1.mga6 | 67.0.3396.62-1.mga6 |
chromium-browserRed Hat:rhel_extras:6 |
before 0:66.0.3359.139-1.el6_9 | 0:66.0.3359.139-1.el6_9 |
chromium-browser-debuginfoRed Hat:rhel_extras:6 |
before 0:66.0.3359.139-1.el6_9 | 0:66.0.3359.139-1.el6_9 |
chromium-browserUbuntu:16.04:LTS |
before 66.0.3359.139-0ubuntu0.16.04.3, plus listed versions 45.0.2454.101-0ubuntu1.120147.0.2526.73-0ubuntu1.121847.0.2526.106-0ubuntu1.122148.0.2564.82-0ubuntu1.122248.0.2564.116-0ubuntu1.1229 Show 29 moreShow less49.0.2623.87-0ubuntu1.123249.0.2623.108-0ubuntu1.123350.0.2661.102-0ubuntu0.16.04.1.123751.0.2704.79-0ubuntu0.16.04.1.124252.0.2743.116-0ubuntu0.16.04.1.125053.0.2785.143-0ubuntu0.16.04.1.125453.0.2785.143-0ubuntu0.16.04.1.125755.0.2883.87-0ubuntu0.16.04.126356.0.2924.76-0ubuntu0.16.04.126857.0.2987.98-0ubuntu0.16.04.127658.0.3029.81-0ubuntu0.16.04.127758.0.3029.96-0ubuntu0.16.04.127958.0.3029.110-0ubuntu0.16.04.128159.0.3071.109-0ubuntu0.16.04.128959.0.3071.109-0ubuntu0.16.04.129160.0.3112.78-0ubuntu0.16.04.129360.0.3112.113-0ubuntu0.16.04.129861.0.3163.79-0ubuntu0.16.04.130061.0.3163.100-0ubuntu0.16.04.130662.0.3202.62-0ubuntu0.16.04.130862.0.3202.75-0ubuntu0.16.04.131362.0.3202.89-0ubuntu0.16.04.131562.0.3202.94-0ubuntu0.16.04.131763.0.3239.84-0ubuntu0.16.04.163.0.3239.132-0ubuntu0.16.04.164.0.3282.119-0ubuntu0.16.04.164.0.3282.140-0ubuntu0.16.04.164.0.3282.167-0ubuntu0.16.04.165.0.3325.181-0ubuntu0.16.04.1 |
66.0.3359.139-0ubuntu0.16.04.3 |
oxide-qtUbuntu:16.04:LTS |
All versions, plus listed versions 1.9.5-0ubuntu11.10.3-0ubuntu0.15.10.11.10.3-0ubuntu0.15.10.21.11.3-0ubuntu31.11.4-0ubuntu1 Show 17 moreShow less1.11.5-0ubuntu11.12.5-0ubuntu11.12.6-0ubuntu11.12.7-0ubuntu11.13.6-0ubuntu11.14.7-0ubuntu11.14.9-0ubuntu0.16.04.11.15.7-0ubuntu0.16.04.11.15.8-0ubuntu0.16.04.11.16.5-0ubuntu0.16.04.11.17.7-0ubuntu0.16.04.11.17.9-0ubuntu0.16.04.11.18.3-0ubuntu0.16.04.11.18.5-0ubuntu0.16.04.11.19.4-0ubuntu0.16.04.11.20.4-0ubuntu0.16.04.11.21.5-0ubuntu0.16.04.1 |
None known |
chromium-browserUbuntu:18.04:LTS |
before 66.0.3359.139-0ubuntu0.18.04.3, plus listed versions 61.0.3163.100-0ubuntu1.137862.0.3202.62-0ubuntu0.17.10.138062.0.3202.89-0ubuntu1.138662.0.3202.94-0ubuntu1.138863.0.3239.84-0ubuntu1 Show 6 moreShow less63.0.3239.108-0ubuntu164.0.3282.119-0ubuntu164.0.3282.140-0ubuntu164.0.3282.167-0ubuntu165.0.3325.146-0ubuntu165.0.3325.181-0ubuntu1 |
66.0.3359.139-0ubuntu0.18.04.3 |
chromiumSUSE:Package Hub 12 SP2 |
before 66.0.3359.181-55.1 | 66.0.3359.181-55.1 |
chromiumopenSUSE:Tumbleweed |
before 93.0.4577.82-1.1 | 93.0.4577.82-1.1 |
chromiumopenSUSE:Tumbleweed |
before 113.0.5672.92-1.1 | 113.0.5672.92-1.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2018-6118 is a high vulnerability (CVSS 8.8) in Google Chrome, published May 27, 2018. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 1.91%, the 79th percentile. Fixed in chromium-browser 67.0.3396.87-1~deb9u1.
References
crbug.com/831963
chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop_26.html
nvd.nist.gov/vuln/detail/CVE-2018-6118
github.com/advisories/GHSA-g93q-r5hj-4m44
advisories.mageia.org/MGASA-2018-0268.html
bugs.mageia.org/show_bug.cgi?id=22138
Show 194 moreShow less
chromereleases.googleblog.com/2018/02/stable-channel-update-for-desktop_13.html
chromereleases.googleblog.com/2018/02/stable-channel-update-for-desktop_22.html
chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html
chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop_13.html
chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop_20.html
chromereleases.googleblog.com/2018/04/stable-channel-update-for-desktop.html
chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop.html
chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop_15.html
chromereleases.googleblog.com/2018/05/stable-channel-update-for-desktop_58.html
access.redhat.com/errata/RHSA-2018:1321
access.redhat.com/security/updates/classification
bugzilla.redhat.com/show_bug.cgi?id=1573856
security.access.redhat.com/data/csaf/v2/advisories/2018/rhsa-2018_1321.json
access.redhat.com/security/cve/CVE-2018-6118
cve.org/CVERecord?id=CVE-2018-6118
ubuntu.com/security/CVE-2018-6118
lists.opensuse.org/archives/list/[email protected]/thread/IDH7ZAFKSWX2J7H7ULZFAVM7KUQXQHZZ
bugzilla.suse.com/1084296
bugzilla.suse.com/1086124
bugzilla.suse.com/1090000
bugzilla.suse.com/1091288
bugzilla.suse.com/1092272
bugzilla.suse.com/1092923
bugzilla.suse.com/1093031
suse.com/security/cve/CVE-2017-11215
suse.com/security/cve/CVE-2017-11225
suse.com/security/cve/CVE-2018-6057
suse.com/security/cve/CVE-2018-6060
suse.com/security/cve/CVE-2018-6061
suse.com/security/cve/CVE-2018-6062
suse.com/security/cve/CVE-2018-6063
suse.com/security/cve/CVE-2018-6064
suse.com/security/cve/CVE-2018-6065
suse.com/security/cve/CVE-2018-6066
suse.com/security/cve/CVE-2018-6067
suse.com/security/cve/CVE-2018-6068
suse.com/security/cve/CVE-2018-6069
suse.com/security/cve/CVE-2018-6070
suse.com/security/cve/CVE-2018-6071
suse.com/security/cve/CVE-2018-6072
suse.com/security/cve/CVE-2018-6073
suse.com/security/cve/CVE-2018-6074
suse.com/security/cve/CVE-2018-6075
suse.com/security/cve/CVE-2018-6076
suse.com/security/cve/CVE-2018-6077
suse.com/security/cve/CVE-2018-6078
suse.com/security/cve/CVE-2018-6079
suse.com/security/cve/CVE-2018-6080
suse.com/security/cve/CVE-2018-6081
suse.com/security/cve/CVE-2018-6082
suse.com/security/cve/CVE-2018-6083
suse.com/security/cve/CVE-2018-6085
suse.com/security/cve/CVE-2018-6086
suse.com/security/cve/CVE-2018-6087
suse.com/security/cve/CVE-2018-6088
suse.com/security/cve/CVE-2018-6089
suse.com/security/cve/CVE-2018-6090
suse.com/security/cve/CVE-2018-6091
suse.com/security/cve/CVE-2018-6092
suse.com/security/cve/CVE-2018-6093
suse.com/security/cve/CVE-2018-6094
suse.com/security/cve/CVE-2018-6095
suse.com/security/cve/CVE-2018-6096
suse.com/security/cve/CVE-2018-6097
suse.com/security/cve/CVE-2018-6098
suse.com/security/cve/CVE-2018-6099
suse.com/security/cve/CVE-2018-6100
suse.com/security/cve/CVE-2018-6101
suse.com/security/cve/CVE-2018-6102
suse.com/security/cve/CVE-2018-6103
suse.com/security/cve/CVE-2018-6104
suse.com/security/cve/CVE-2018-6105
suse.com/security/cve/CVE-2018-6106
suse.com/security/cve/CVE-2018-6107
suse.com/security/cve/CVE-2018-6108
suse.com/security/cve/CVE-2018-6109
suse.com/security/cve/CVE-2018-6110
suse.com/security/cve/CVE-2018-6111
suse.com/security/cve/CVE-2018-6112
suse.com/security/cve/CVE-2018-6113
suse.com/security/cve/CVE-2018-6114
suse.com/security/cve/CVE-2018-6115
suse.com/security/cve/CVE-2018-6116
suse.com/security/cve/CVE-2018-6117
suse.com/security/cve/CVE-2018-6118
suse.com/security/cve/CVE-2018-6120
suse.com/security/cve/CVE-2018-6121
suse.com/security/cve/CVE-2018-6122
lists.opensuse.org/archives/list/[email protected]/thread/2DBOODMITDSXVHCJIIPL7JVX44YVOERP
suse.com/security/cve/CVE-2017-15386
suse.com/security/cve/CVE-2017-15387
suse.com/security/cve/CVE-2017-15388
suse.com/security/cve/CVE-2017-15389
suse.com/security/cve/CVE-2017-15390
suse.com/security/cve/CVE-2017-15391
suse.com/security/cve/CVE-2017-15392
suse.com/security/cve/CVE-2017-15393
suse.com/security/cve/CVE-2017-15394
suse.com/security/cve/CVE-2017-15395
suse.com/security/cve/CVE-2017-15396
suse.com/security/cve/CVE-2017-15398
suse.com/security/cve/CVE-2017-15399
suse.com/security/cve/CVE-2017-15407
suse.com/security/cve/CVE-2017-15408
suse.com/security/cve/CVE-2017-15409
suse.com/security/cve/CVE-2017-15410
suse.com/security/cve/CVE-2017-15411
suse.com/security/cve/CVE-2017-15412
suse.com/security/cve/CVE-2017-15413
suse.com/security/cve/CVE-2017-15415
suse.com/security/cve/CVE-2017-15416
suse.com/security/cve/CVE-2017-15417
suse.com/security/cve/CVE-2017-15418
suse.com/security/cve/CVE-2017-15419
suse.com/security/cve/CVE-2017-15420
suse.com/security/cve/CVE-2017-15422
suse.com/security/cve/CVE-2017-15423
suse.com/security/cve/CVE-2017-15424
suse.com/security/cve/CVE-2017-15425
suse.com/security/cve/CVE-2017-15426
suse.com/security/cve/CVE-2017-15427
suse.com/security/cve/CVE-2017-15429
suse.com/security/cve/CVE-2017-15430
suse.com/security/cve/CVE-2017-5006
suse.com/security/cve/CVE-2017-5007
suse.com/security/cve/CVE-2017-5008
suse.com/security/cve/CVE-2017-5009
suse.com/security/cve/CVE-2017-5010
suse.com/security/cve/CVE-2017-5011
suse.com/security/cve/CVE-2017-5012
suse.com/security/cve/CVE-2017-5013
suse.com/security/cve/CVE-2017-5014
suse.com/security/cve/CVE-2017-5015
suse.com/security/cve/CVE-2017-5016
suse.com/security/cve/CVE-2017-5017
suse.com/security/cve/CVE-2017-5018
suse.com/security/cve/CVE-2017-5019
suse.com/security/cve/CVE-2017-5020
suse.com/security/cve/CVE-2017-5021
suse.com/security/cve/CVE-2017-5022
suse.com/security/cve/CVE-2017-5023
suse.com/security/cve/CVE-2017-5024
suse.com/security/cve/CVE-2017-5025
suse.com/security/cve/CVE-2017-5026
suse.com/security/cve/CVE-2017-5030
suse.com/security/cve/CVE-2017-5035
suse.com/security/cve/CVE-2017-5041
suse.com/security/cve/CVE-2017-5044
suse.com/security/cve/CVE-2017-5052
suse.com/security/cve/CVE-2017-5053
suse.com/security/cve/CVE-2017-5054
suse.com/security/cve/CVE-2017-5055
suse.com/security/cve/CVE-2017-5056
suse.com/security/cve/CVE-2017-5057
suse.com/security/cve/CVE-2017-5058
suse.com/security/cve/CVE-2017-5059
suse.com/security/cve/CVE-2017-5060
suse.com/security/cve/CVE-2017-5061
suse.com/security/cve/CVE-2017-5062
suse.com/security/cve/CVE-2017-5063
suse.com/security/cve/CVE-2017-5064
suse.com/security/cve/CVE-2017-5065
suse.com/security/cve/CVE-2017-5066
suse.com/security/cve/CVE-2017-5067
suse.com/security/cve/CVE-2017-5068
suse.com/security/cve/CVE-2017-5069
suse.com/security/cve/CVE-2017-5070
suse.com/security/cve/CVE-2017-5071
suse.com/security/cve/CVE-2017-5072
suse.com/security/cve/CVE-2017-5073
suse.com/security/cve/CVE-2017-5074
suse.com/security/cve/CVE-2017-5075
suse.com/security/cve/CVE-2017-5076
suse.com/security/cve/CVE-2017-5077
suse.com/security/cve/CVE-2017-5078
suse.com/security/cve/CVE-2017-5079
suse.com/security/cve/CVE-2017-5080
suse.com/security/cve/CVE-2017-5081
suse.com/security/cve/CVE-2017-5082
suse.com/security/cve/CVE-2017-5083
suse.com/security/cve/CVE-2017-5085
suse.com/security/cve/CVE-2017-5086
suse.com/security/cve/CVE-2017-5087
suse.com/security/cve/CVE-2017-5088
suse.com/security/cve/CVE-2017-5089
suse.com/security/cve/CVE-2017-5091
suse.com/security/cve/CVE-2017-5092
suse.com/security/cve/CVE-2017-5093
suse.com/security/cve/CVE-2017-5094
suse.com/security/cve/CVE-2017-5095
suse.com/security/cve/CVE-2017-5096
suse.com/security/cve/CVE-2017-5097
suse.com/security/cve/CVE-2017-5098
suse.com/security/cve/CVE-2017-5099
Left out here: 2,141 references. The JSON record has them.