CVE-2013-4392

MEDIUMNVD 5.05.0—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
5.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 5.0Exploit: None knownExposed services: Not assessed

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

systemd, when updating file permissions, allows local users to change the permissions and SELinux security contexts for arbitrary files via a symlink attack on unspecified files.

CVSS v3
5.0
EG Score
5.0MEDIUMmedium confidence
EG Risk
23
EG Risk 23/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
Severity50% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.5%
EPSS %ILE
38th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). 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

October 28, 2013

Last Modified

April 29, 2026

References (6)

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
systemd247.3-6 ... 261~rc4-1 (279 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
systemd252.11-1 ... 261~rc4-1 (183 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
systemd257.13-1~deb13u1 ... 261~rc4-1 (35 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
systemd257.13-1~deb13u1 ... 261~rc4-1 (35 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 17× 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 146 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2013-4392?
CVE-2013-4392 is a medium vulnerability published on October 28, 2013. systemd, when updating file permissions, allows local users to change the permissions and SELinux security contexts for arbitrary files via a symlink attack on unspecified files.
When was CVE-2013-4392 disclosed?
CVE-2013-4392 was first published on October 28, 2013, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2013-4392 actively exploited?
CVE-2013-4392 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2013-4392?
CVE-2013-4392 has a CVSS v3 base score of 5.0 (NVD).
How do I remediate CVE-2013-4392?
No fix for CVE-2013-4392 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-2013-4392

Explore →

Is Your Infrastructure Affected by CVE-2013-4392?

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

Book a Demo →Browse All CVEs