CVE-2013-1591

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

Stack-based buffer overflow in libpixman, as used in Pale Moon before 15.4 and possibly other products, has unspecified impact and context-dependent attack vectors. NOTE: this issue might be resultant from an integer overflow in the fast_composite_scaled_bilinear function in pixman-inlines.h, which triggers an infinite loop.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
88.1%
KEV
Not listed

Published

January 31, 2013

Last Modified

April 29, 2026

Advisory Details (5)

Auto-updated May 10, 2026
Patch available. Sources: redhat.
redhat Patch Available

910149 – (CVE-2013-1591) CVE-2013-1591 pixman: stack-based buffer overflow

Affected: Red Hat Enterprise Linux 5 or 6 (the fast_composite_scaled_bilinear() function is in pixman/pixman-fast-path.h, but the vulner

https://bugzilla.redhat.com/show_bug.cgi?id=910149
generic

Support/Advisories/MGASA-2013-0077 - Mageia wiki

https://wiki.mageia.org/en/Support/Advisories/MGASA-2013-0077

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhev-hypervisor6-0:6.4-20130415.0.el6_42013-04-23redhat
redhatpixman-0:0.26.2-5.el6_42013-03-27redhat

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.

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 7× in last 7d / 35× 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 101 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2013-1591?
CVE-2013-1591 is a critical vulnerability published on January 31, 2013. Stack-based buffer overflow in libpixman, as used in Pale Moon before 15.4 and possibly other products, has unspecified impact and context-dependent attack vectors. NOTE: this issue might be resultant from an integer overflow in the fastcompositescaled_bilinear function in pixman-inlines.h, which…
When was CVE-2013-1591 disclosed?
CVE-2013-1591 was first published in the National Vulnerability Database on January 31, 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-1591 actively exploited?
CVE-2013-1591 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 88.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2013-1591?
CVE-2013-1591 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2013-1591?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2013-1591, 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-2013-1591

Explore →

Is Your Infrastructure Affected by CVE-2013-1591?

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