CVE-2006-4663

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory published 2022-05-01. NVD baseline CVSS 7.8; sources differ by 0.0.

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

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

The source code tar archive of the Linux kernel 2.6.16, 2.6.17.11, and possibly other versions specifies weak permissions (0666 and 0777) for certain files and directories, which might allow local users to insert Trojan horse source code that would be used during the next kernel compilation. NOTE: another researcher disputes the vulnerability, stating that he finds "Not a single world-writable file or directory." CVE analysis as of 20060908 indicates that permissions will only be weak under certain unusual or insecure scenarios

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

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%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
26%
KEV
Not listed

Published

September 9, 2006

Last Modified

April 16, 2026

Advisory Details (2)

Auto-updated May 31, 2026
No patch confirmed yet.
generic
http://www.securityfocus.com/archive/1/445540/100/0/threaded
generic
http://www.securityfocus.com/archive/1/445539/100/0/threaded

Data Freshness Timeline

(refreshed 3× in last 7d / 4× 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.

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

Frequently asked(5)

What is CVE-2006-4663?
CVE-2006-4663 is a high vulnerability published on September 9, 2006. The source code tar archive of the Linux kernel 2.6.16, 2.6.17.11, and possibly other versions specifies weak permissions (0666 and 0777) for certain files and directories, which might allow local users to insert Trojan horse source code that would be used during the next kernel compilation. NOTE:…
When was CVE-2006-4663 disclosed?
CVE-2006-4663 was first published in the National Vulnerability Database on September 9, 2006, with the most recent update on April 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2006-4663 actively exploited?
CVE-2006-4663 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 74.1% of all scored CVEs.
What is the CVSS score of CVE-2006-4663?
CVE-2006-4663 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2006-4663?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2006-4663, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2006-4663

Explore →

Is Your Infrastructure Affected by CVE-2006-4663?

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

Start Free Scan →Browse All CVEs