CVE-2007-1536

HIGHCVSS v2 · 9.39.3—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 9.3 — v2 rates that HIGH (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:M/Au:N/C:C/I:C/A:C. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 13.5% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Sources: epss, nvd_v2
Weaponized
9.3EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • Public exploit code is available (Exploit-DB (verified), epss top5pct, public exploit)
CISA-KEV: Not listedEPSS PROB: 13%CVSS v2: 9.3Exploit: Exploit-DB (verified) · epss top5pct · public exploitExposed services: Not assessed

A fix is available — apply it.

Integer underflow in the file_printf function in the "file" program before 4.20 allows user-assisted attackers to execute arbitrary code via a file that triggers a heap-based buffer overflow.

CVSS v2.0 (legacy)
9.3HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
9.3HIGHlow confidence
EG Risk
72
EG Risk 72/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
Severity93% × 45%
Exploitation65% × 40%
Automatability30% × 15%
CISA SSVC: Track at low, Track or Track* at medium and Track* or Attend at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
13%
EPSS %ILE
96th
KEV
Not listed

CISA SSVCTrack at low, Track or Track* at medium and Track* or Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (EG-KEV: weaponized) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). 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

March 20, 2007

Last Modified

April 23, 2026

References (86)

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibmagic1 (4.17-2ubuntu1.1) @ edgy2026-05-31ubuntu
redhatfile-0:4.17-9.el52007-03-23redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(6 across 6 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
file—4.20-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
file—4.20-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
file—4.20-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
file—4.20-1—
Debian:3.1(1)
PackageVulnerable rangeFixed inDependents
file4.12-14.12-1sarge1—
Debian:4.0(1)
PackageVulnerable rangeFixed inDependents
file—4.17-5etch1—

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 1× in last 7d / 10× 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 105 total refreshes for this CVE.

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

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-29753✓ verified
    First seen Mar 19, 2007

    File(1) 4.13 - Command File_PrintF Integer Underflow

    Open source ↗

Related CVEs(same product)

Frequently asked(4)

What is CVE-2007-1536?
CVE-2007-1536 is a high vulnerability published on March 20, 2007. Integer underflow in the file_printf function in the "file" program before 4.20 allows user-assisted attackers to execute arbitrary code via a file that triggers a heap-based buffer overflow.
When was CVE-2007-1536 disclosed?
CVE-2007-1536 was first published on March 20, 2007, with the most recent update on April 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2007-1536 actively exploited?
CVE-2007-1536 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model classifies it as weaponized: a functional public exploit exists. FIRST EPSS estimates a 13% probability of exploitation in the next 30 days (96th percentile of EPSS-scored CVEs).
How do I remediate CVE-2007-1536?
A fix for CVE-2007-1536 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2007-1536

Explore →

Is Your Infrastructure Affected by CVE-2007-1536?

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

Book a Demo →Browse All CVEs