Spreadsheet::ParseExcel version 0.65 is a Perl module used for parsing Excel files. Spreadsheet::ParseExcel is vulnerable to an arbitrary code execution (ACE) vulnerability due to passing unvalidated input from a file into a string-type “eval”. Specifically, the issue stems from the evaluation of Number format strings (not to be confused with printf-style format strings) within the Excel parsing logic.
CVE-2023-7101
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2024-01-02), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.8 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
A fix is available — apply it.
- CVSS v3
- 7.8
- EG Score
- 9.0(high)
- EG Risk
- 81(Attend)EG Risk 81/100SSVC: Attend
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 computedSeverity90% × 45%Exploitation100% × 40%Automatability0% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 19%
- EPSS %ILE
- 97%
- KEV
- ⚠ Exploited
Published
December 24, 2023
Last Modified
June 17, 2026
Advisory Details (6)
Auto-updated Jun 4, 2026[SECURITY] Fedora 38 Update: perl-Spreadsheet-ParseExcel-0.6600-1.fc38 - package-announce - Fedora mailing-lists
https://lists.fedoraproject.org/archives/list/[email protected]/message/M2FIWDHRYTAAQLGM6AFOZVM7AFZ4H2ZR/[SECURITY] Fedora 39 Update: perl-Spreadsheet-ParseExcel-0.6600-1.fc39 - package-announce - Fedora mailing-lists
https://lists.fedoraproject.org/archives/list/[email protected]/message/IFEHKULQRVXHIV7XXK2RGD4VQN6Y4CV5/[SECURITY] [DLA 3702-1] libspreadsheet-parseexcel-perl security update
https://lists.debian.org/debian-lts-announce/2023/12/msg00025.htmlVulnerability-Disclosures/2023/MNDT-2023-0019.md at master · mandiant/Vulnerability-Disclosures · GitHub
https://github.com/mandiant/Vulnerability-Disclosures/blob/master/2023/MNDT-2023-0019.mdspreadsheet-parseexcel/lib/Spreadsheet/ParseExcel/Utility.pm at c7298592e102a375d43150cd002feed806557c15 · jmcnamara/spreadsheet-parseexcel · GitHub
https://github.com/jmcnamara/spreadsheet-parseexcel/blob/c7298592e102a375d43150cd002feed806557c15/lib/Spreadsheet/ParseExcel/Utility.pm#L171oss-security - CVE-2023-7101: Spreadsheet::ParseExcel for Perl is vulnerable to arbitrary code execution
http://www.openwall.com/lists/oss-security/2023/12/29/4Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | libspreadsheet-parseexcel-perl (0.6500-1ubuntu0.16.04.1~esm1) @ xenial | 2026-09-19 | ubuntu |
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
(5 across 5 ecosystems)
Debian:10(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libspreadsheet-parseexcel-perl | 0.6500-1 | 0.6500-1+deb10u1 | — |
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libspreadsheet-parseexcel-perl | 0.6500-1.1 | 0.6500-1.1+deb11u1 | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libspreadsheet-parseexcel-perl | 0.6500-3 | 0.6500-4~deb12u1 | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libspreadsheet-parseexcel-perl | — | 0.6500-4 | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| libspreadsheet-parseexcel-perl | — | 0.6500-4 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
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 100× in last 7d / 396× 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 1,409 total refreshes for this CVE.
- 2026-09-19 06:41 UTCVendor advisory
- 2026-09-19 06:40 UTCGHSA enrichment
- 2026-09-19 02:49 UTCVendor advisory
- 2026-09-19 02:49 UTCGHSA enrichment
- 2026-09-18 22:57 UTCEG score recompute
- 2026-09-18 22:57 UTCVendor advisory
- 2026-09-18 22:57 UTCGHSA enrichment
- 2026-09-18 19:26 UTCEPSS rescore
- 2026-09-18 19:20 UTCCISA KEV update
- 2026-09-18 19:06 UTCVendor advisory
- 2026-09-18 19:06 UTCGHSA enrichment
- 2026-09-18 15:15 UTCGHSA enrichment
- 2026-09-18 14:15 UTCCISA KEV update
- 2026-09-18 11:24 UTCVendor advisory
- 2026-09-18 11:24 UTCGHSA enrichment
- 2026-09-18 07:33 UTCVendor advisory
- 2026-09-18 07:33 UTCGHSA enrichment
- 2026-09-18 03:42 UTCVendor advisory
- 2026-09-18 03:42 UTCGHSA enrichment
- 2026-09-17 23:50 UTCVendor advisory
- 2026-09-17 23:50 UTCGHSA enrichment
- 2026-09-17 19:58 UTCEG score recompute
- 2026-09-17 19:58 UTCVendor advisory
- 2026-09-17 19:58 UTCGHSA enrichment
- 2026-09-17 16:07 UTCVendor advisory
Show 75 moreShow fewer
- 2026-09-17 16:07 UTCGHSA enrichment
- 2026-09-17 12:15 UTCVendor advisory
- 2026-09-17 12:15 UTCGHSA enrichment
- 2026-09-17 08:24 UTCVendor advisory
- 2026-09-17 08:24 UTCGHSA enrichment
- 2026-09-17 04:32 UTCVendor advisory
- 2026-09-17 04:32 UTCGHSA enrichment
- 2026-09-17 00:41 UTCVendor advisory
- 2026-09-17 00:41 UTCGHSA enrichment
- 2026-09-16 20:49 UTCGHSA enrichment
- 2026-09-16 16:56 UTCEG score recompute
- 2026-09-16 16:56 UTCGHSA enrichment
- 2026-09-16 14:10 UTCCISA KEV update
- 2026-09-16 14:06 UTCEPSS rescore
- 2026-09-16 13:04 UTCVendor advisory
- 2026-09-16 13:04 UTCGHSA enrichment
- 2026-09-16 09:13 UTCVendor advisory
- 2026-09-16 09:13 UTCGHSA enrichment
- 2026-09-16 05:22 UTCEG score recompute
- 2026-09-16 05:22 UTCVendor advisory
- 2026-09-16 05:21 UTCGHSA enrichment
- 2026-09-16 05:11 UTCEPSS rescore
- 2026-09-16 05:11 UTCEPSS rescore
- 2026-09-16 01:30 UTCVendor advisory
- 2026-09-16 01:30 UTCGHSA enrichment
- 2026-09-15 21:38 UTCVendor advisory
- 2026-09-15 21:38 UTCGHSA enrichment
- 2026-09-15 17:46 UTCVendor advisory
- 2026-09-15 17:46 UTCGHSA enrichment
- 2026-09-15 13:55 UTCVendor advisory
- 2026-09-15 13:55 UTCGHSA enrichment
- 2026-09-15 10:03 UTCVendor advisory
- 2026-09-15 10:03 UTCGHSA enrichment
- 2026-09-15 06:12 UTCEG score recompute
- 2026-09-15 06:12 UTCVendor advisory
- 2026-09-15 06:12 UTCGHSA enrichment
- 2026-09-15 03:08 UTCEPSS rescore
- 2026-09-15 02:19 UTCVendor advisory
- 2026-09-15 02:19 UTCGHSA enrichment
- 2026-09-14 22:27 UTCVendor advisory
- 2026-09-14 22:27 UTCGHSA enrichment
- 2026-09-14 19:24 UTCCISA KEV update
- 2026-09-14 18:36 UTCVendor advisory
- 2026-09-14 18:36 UTCGHSA enrichment
- 2026-09-14 14:43 UTCVendor advisory
- 2026-09-14 14:43 UTCGHSA enrichment
- 2026-09-14 10:52 UTCVendor advisory
- 2026-09-14 10:52 UTCGHSA enrichment
- 2026-09-14 07:01 UTCVendor advisory
- 2026-09-14 07:01 UTCGHSA enrichment
- 2026-09-14 03:10 UTCVendor advisory
- 2026-09-14 03:10 UTCGHSA enrichment
- 2026-09-13 23:19 UTCVendor advisory
- 2026-09-13 23:19 UTCGHSA enrichment
- 2026-09-13 19:28 UTCVendor advisory
- 2026-09-13 19:28 UTCGHSA enrichment
- 2026-09-13 15:36 UTCGHSA enrichment
- 2026-09-13 11:42 UTCVendor advisory
- 2026-09-13 11:42 UTCGHSA enrichment
- 2026-09-13 07:50 UTCVendor advisory
- 2026-09-13 07:50 UTCGHSA enrichment
- 2026-09-13 04:00 UTCVendor advisory
- 2026-09-13 03:59 UTCGHSA enrichment
- 2026-09-13 00:08 UTCVendor advisory
- 2026-09-13 00:08 UTCGHSA enrichment
- 2026-09-12 20:16 UTCVendor advisory
- 2026-09-12 20:16 UTCGHSA enrichment
- 2026-09-12 16:24 UTCEG score recompute
- 2026-09-12 16:24 UTCVendor advisory
- 2026-09-12 16:24 UTCGHSA enrichment
- 2026-09-12 14:58 UTCEPSS rescore
- 2026-09-12 12:33 UTCVendor advisory
- 2026-09-12 12:33 UTCGHSA enrichment
- 2026-09-12 08:42 UTCVendor advisory
- 2026-09-12 08:42 UTCGHSA enrichment
Publicly available exploits
(1 reference)Working exploit code is in the public domain (1 Metasploit module). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- Metasploitexploit/linux/smtp/barracuda_esg_spreadsheet_rce✓ verifiedFirst seen Dec 24, 2023
Barracuda ESG Spreadsheet::ParseExcel Arbitrary Code Execution
Open source ↗
Frequently asked(6)
What is CVE-2023-7101?
When was CVE-2023-7101 disclosed?
Is CVE-2023-7101 actively exploited?
What is the CVSS score of CVE-2023-7101?
Which products are affected by CVE-2023-7101?
How do I remediate CVE-2023-7101?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-7101
Is Your Infrastructure Affected by CVE-2023-7101?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.