Public mode

No access to your tenant or devices. Every item links to its source. What this means

CVE-2007-0671CISA KEV

Microsoft Office Excel Remote Code Execution Vulnerability

Severity unknownCVSS unknownCheck the vendor advisory for fixed versions

CISA lists this Microsoft vulnerability as known exploited. Its MSRC release detail is outside this installation's collected history.

CISA KEV Check MSRC

CISA catalog record

Microsoft Office Excel contains a remote code execution vulnerability that can be exploited when a specially crafted Excel file is opened. This malicious file could be delivered as an email attachment or hosted on a malicious website. An attacker could leverage this vulnerability by creating a specially crafted Excel file, which, when opened, allowing an attacker to execute remote code on the affected system.

Product: Office
Added to KEV: 12 Aug 2025
Federal remediation due: 2 Sep 2025
Known ransomware use: Not reported

Page history

Changes are dated when recorded; day views use the last saved version from that UTC day, and citations stay fixed.

Cite this version

Field-level log (2)

Up to 100 recent field edits are shown; older edits may be outside retention.

23 Oct 2026 · 09:33:49 UTC Source coverage: cisa-kevIncomplete → Current
23 Oct 2026 · 08:31:50 UTC Source coverage: cisa-kevCurrent → Incomplete

Explore global source statements, affected packages and advisory history for CVE-2007-0671. The catalog has a separate collection scope from Microsoft release records.

More advisories, affected versions and source history

cve-program · CVE-2007-0671

Published

n/a

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "product": "n/a",
                    "vendor": "n/a",
                    "versions": [
                        {
                            "status": "affected",
                            "version": "n/a"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON