CVE-2018-19358

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2022-05-13. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.8Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

GNOME Keyring through 3.28.2 allows local users to retrieve login credentials via a Secret Service API call and the D-Bus interface if the keyring is unlocked, a similar issue to CVE-2008-7320. One perspective is that this occurs because available D-Bus protection mechanisms (involving the busconfig and policy XML elements) are not used. NOTE: the vendor disputes this because, according to the security model, untrusted applications must not be allowed to access the user's session bus socket.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation1% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.6%
EPSS %ILE
44th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

November 18, 2018

Last Modified

November 21, 2024

Advisory Details (5)

Auto-updated Sep 28, 2026
No fix on record yet. Sources: redhat.
generic
https://www.youtube.com/watch?v=Do4E9ZQaPck
generic

[CVE-2018-19358] Credentials located in gnome-keyring can be compromised easily. (#5) · Issues · GNOME / gnome-keyring · GitLab

https://gitlab.gnome.org/GNOME/gnome-keyring/-/issues/5#note_1876550
generic

GitHub - sungjungk/keyring_crack · GitHub

https://github.com/sungjungk/keyring_crack
redhat

1652194 – (CVE-2018-19358) CVE-2018-19358 gnome-keyring: login credentials retrieval via a Secret Service API call

https://bugzilla.redhat.com/show_bug.cgi?id=1652194#c8
generic

Bug #1780365 “Credentials located in gnome-keyring can be compro...” : Bugs : gnome-keyring package : Ubuntu

https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1780365

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
gnome-keyring3.36.0-1 ... 50.0-1 (18 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
gnome-keyring42.1-1 ... 50.0-1 (14 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
gnome-keyring48.0-1 ... 50.0-1 (6 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
gnome-keyring48.0-1 ... 50.0-1 (6 versions)
  • every version on: no fix on record
—

Data Freshness Timeline

(refreshed 6× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 167 total refreshes for this CVE.

  1. 2026-10-05 17:39 UTCEPSS rescore
  2. 2026-10-04 23:18 UTCEPSS rescore
  3. 2026-10-03 14:21 UTCEPSS rescore
  4. 2026-10-01 19:44 UTCEPSS rescore
  5. 2026-09-30 14:59 UTCEPSS rescore
  6. 2026-09-30 09:58 UTCEG score recompute
  7. 2026-09-28 16:13 UTCOSV refresh
  8. 2026-09-28 13:45 UTCEPSS rescore
  9. 2026-09-27 13:40 UTCEPSS rescore
  10. 2026-09-26 15:53 UTCEPSS rescore
  11. 2026-09-24 13:59 UTCEPSS rescore
  12. 2026-09-24 13:59 UTCEPSS rescore
  13. 2026-09-20 20:10 UTCEPSS rescore
  14. 2026-09-19 15:36 UTCEPSS rescore
  15. 2026-09-18 19:22 UTCEPSS rescore
  16. 2026-09-17 19:22 UTCEPSS rescore
  17. 2026-09-16 05:06 UTCEPSS rescore
  18. 2026-09-15 03:05 UTCEPSS rescore
  19. 2026-09-13 16:42 UTCEPSS rescore
  20. 2026-09-12 14:56 UTCEPSS rescore
  21. 2026-09-11 14:47 UTCEPSS rescore
  22. 2026-09-11 09:32 UTCEPSS rescore
  23. 2026-09-08 21:04 UTCOSV refresh
  24. 2026-09-07 15:57 UTCEPSS rescore
  25. 2026-09-06 13:43 UTCEPSS rescore
Show 75 more
  1. 2026-09-05 15:24 UTCEPSS rescore
  2. 2026-09-04 13:56 UTCEPSS rescore
  3. 2026-09-04 05:02 UTCEPSS rescore
  4. 2026-09-02 14:07 UTCEPSS rescore
  5. 2026-09-01 13:49 UTCEPSS rescore
  6. 2026-09-01 03:32 UTCEPSS rescore
  7. 2026-08-28 21:36 UTCEPSS rescore
  8. 2026-08-27 14:21 UTCEPSS rescore
  9. 2026-08-26 14:42 UTCEPSS rescore
  10. 2026-08-25 13:44 UTCEPSS rescore
  11. 2026-08-22 06:07 UTCOSV refresh
  12. 2026-08-21 23:45 UTCEPSS rescore
  13. 2026-08-20 22:51 UTCEPSS rescore
  14. 2026-08-19 17:00 UTCEPSS rescore
  15. 2026-08-18 13:44 UTCEPSS rescore
  16. 2026-08-17 13:43 UTCEPSS rescore
  17. 2026-08-16 14:51 UTCEPSS rescore
  18. 2026-08-16 02:10 UTCEPSS rescore
  19. 2026-08-15 01:26 UTCEPSS rescore
  20. 2026-08-13 21:56 UTCEPSS rescore
  21. 2026-08-12 13:46 UTCEPSS rescore
  22. 2026-08-09 13:43 UTCEPSS rescore
  23. 2026-08-08 16:32 UTCEPSS rescore
  24. 2026-08-07 16:23 UTCEPSS rescore
  25. 2026-08-06 13:42 UTCEPSS rescore
  26. 2026-08-06 09:15 UTCOSV refresh
  27. 2026-08-05 19:13 UTCEPSS rescore
  28. 2026-08-04 15:05 UTCEPSS rescore
  29. 2026-08-02 02:23 UTCEPSS rescore
  30. 2026-08-01 04:12 UTCEPSS rescore
  31. 2026-07-30 16:24 UTCEPSS rescore
  32. 2026-07-30 01:27 UTCEPSS rescore
  33. 2026-07-28 15:32 UTCEPSS rescore
  34. 2026-07-26 14:51 UTCEPSS rescore
  35. 2026-07-26 14:51 UTCEPSS rescore
  36. 2026-07-25 14:14 UTCEPSS rescore
  37. 2026-07-24 14:14 UTCEPSS rescore
  38. 2026-07-24 14:14 UTCEPSS rescore
  39. 2026-07-23 14:15 UTCEPSS rescore
  40. 2026-07-23 01:35 UTCEG score recompute
  41. 2026-07-22 22:15 UTCEG score recompute
  42. 2026-07-22 14:05 UTCEPSS rescore
  43. 2026-07-21 15:22 UTCEPSS rescore
  44. 2026-07-21 02:47 UTCOSV refresh
  45. 2026-07-20 17:04 UTCEPSS rescore
  46. 2026-07-20 17:04 UTCEPSS rescore
  47. 2026-07-19 14:28 UTCEPSS rescore
  48. 2026-07-19 02:26 UTCEPSS rescore
  49. 2026-07-19 02:26 UTCEPSS rescore
  50. 2026-07-16 16:59 UTCEPSS rescore
  51. 2026-07-16 16:59 UTCEPSS rescore
  52. 2026-07-15 16:55 UTCEPSS rescore
  53. 2026-07-15 16:55 UTCEPSS rescore
  54. 2026-07-15 01:56 UTCEPSS rescore
  55. 2026-07-15 01:56 UTCEPSS rescore
  56. 2026-07-13 22:27 UTCEPSS rescore
  57. 2026-07-13 22:26 UTCEPSS rescore
  58. 2026-07-13 06:10 UTCEPSS rescore
  59. 2026-07-12 05:43 UTCEPSS rescore
  60. 2026-07-11 08:24 UTCEPSS rescore
  61. 2026-07-09 19:06 UTCEPSS rescore
  62. 2026-07-08 15:11 UTCEPSS rescore
  63. 2026-07-07 13:42 UTCEPSS rescore
  64. 2026-07-07 13:42 UTCEPSS rescore
  65. 2026-07-06 16:24 UTCEPSS rescore
  66. 2026-07-06 16:24 UTCEPSS rescore
  67. 2026-07-06 02:20 UTCEPSS rescore
  68. 2026-07-05 02:27 UTCEPSS rescore
  69. 2026-07-04 06:28 UTCEPSS rescore
  70. 2026-07-04 06:28 UTCEPSS rescore
  71. 2026-07-03 21:56 UTCOSV refresh
  72. 2026-07-02 16:54 UTCEPSS rescore
  73. 2026-07-01 15:03 UTCEPSS rescore
  74. 2026-07-01 15:03 UTCEPSS rescore
  75. 2026-06-30 23:20 UTCEPSS rescore

Related CVEs(same product)

Frequently asked(5)

What is CVE-2018-19358?
CVE-2018-19358 is a high vulnerability published on November 18, 2018. GNOME Keyring through 3.28.2 allows local users to retrieve login credentials via a Secret Service API call and the D-Bus interface if the keyring is unlocked, a similar issue to CVE-2008-7320. One perspective is that this occurs because available D-Bus protection mechanisms (involving the…
When was CVE-2018-19358 disclosed?
CVE-2018-19358 was first published on November 18, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-19358 actively exploited?
CVE-2018-19358 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2018-19358?
CVE-2018-19358 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2018-19358?
No fix for CVE-2018-19358 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2018-19358

Explore →

Is Your Infrastructure Affected by CVE-2018-19358?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs