You are using an out of date browser. It may not display this or other websites correctly. You should upgrade or use an alternative browser.
cvss scoring
About this tag
The cvss scoring tag on WindowsForum.com covers discussions about the Common Vulnerability Scoring System, particularly how CVSS Attack Vector (AV) values relate to Microsoft's vulnerability advisories. Threads explain apparent contradictions where Microsoft labels a flaw as Remote Code Execution while CVSS shows AV:L (Local), clarifying that the CVE title describes the impact while CVSS AV describes where the exploit trigger occurs. Examples include Excel and Office parsing vulnerabilities where malicious files are delivered remotely but executed locally. The tag focuses on interpreting CVSS vectors correctly, distinguishing between attacker origin and technical trigger conditions, and understanding Microsoft's advisory naming conventions.
Microsoft’s naming here is not contradictory once you separate the attack vector from the effect. In CVSS, AV:L means the exploit requires local interaction on the target machine, or a local foothold in the attack path, while Remote Code Execution in Microsoft’s title describes the impact: the...
Microsoft’s advisory for CVE-2026-26110 labels the defect as a “Remote Code Execution” (RCE) vulnerability in Microsoft Office, yet the published CVSS Attack Vector is listed as Local (AV:L) — this apparent contradiction is deliberate and explains two different questions about risk: who can...
Microsoft’s CVE-2026-20957 advisory names the flaw as a “Microsoft Excel Remote Code Execution Vulnerability,” yet the published CVSS vector lists the Attack Vector as Local (AV:L) — a pairing that looks contradictory until you separate attacker origin and operational impact from the technical...
Microsoft’s brief CVE title and the CVSS vector are answering two different questions: the CVE headline tells you what an off‑host attacker can ultimately accomplish (arbitrary code execution on a target), while the CVSS Attack Vector (AV) reports where the vulnerable code must be executed at...