CVE-2026-81821

HIGHPre-NVD 8.48.4—
EchelonGraph scoreHIGH confidence

Score 8.4 from GitHub Security Advisory (severity: HIGH) published 2026-09-08. a secondary CVSS source baseline 8.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.4Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The vulnerability, if exploited, could allow a miscreant with read access to PIMBoards project files to decrypt and view sensitive information.

CVSS v3
8.4
EG Score
8.4(high)
EG Risk
38(Track)
EG Risk 38/100SSVC: Track

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
Severity84% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

September 8, 2026

Last Modified

September 11, 2026

Advisory Details (1)

Auto-updated Sep 8, 2026
No patch confirmed yet.
generic
https://www.aveva.com/content/dam/aveva/documents/support/cyber-security-updates/SecurityBulletin_AVEVA-2026-006.pdf

Vendor Advisories for CVE-2026-81821(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 21× in last 7d / 40× 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.

  1. 2026-09-19 07:45 UTCEG score recompute
  2. 2026-09-19 07:45 UTCGHSA enrichment
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 18:35 UTCGHSA enrichment
  5. 2026-09-18 05:18 UTCEG score recompute
  6. 2026-09-18 05:18 UTCGHSA enrichment
  7. 2026-09-17 16:10 UTCGHSA enrichment
  8. 2026-09-17 03:02 UTCEG score recompute
  9. 2026-09-17 03:02 UTCGHSA enrichment
  10. 2026-09-16 14:08 UTCEPSS rescore
  11. 2026-09-16 13:54 UTCGHSA enrichment
  12. 2026-09-16 00:41 UTCGHSA enrichment
  13. 2026-09-15 11:26 UTCEG score recompute
  14. 2026-09-15 11:26 UTCGHSA enrichment
  15. 2026-09-15 03:12 UTCEPSS rescore
  16. 2026-09-15 03:12 UTCEPSS rescore
  17. 2026-09-14 22:18 UTCGHSA enrichment
  18. 2026-09-14 09:10 UTCGHSA enrichment
  19. 2026-09-13 20:02 UTCEG score recompute
  20. 2026-09-13 20:02 UTCGHSA enrichment
  21. 2026-09-13 06:54 UTCGHSA enrichment
  22. 2026-09-12 17:46 UTCEG score recompute
  23. 2026-09-12 17:46 UTCGHSA enrichment
  24. 2026-09-12 04:38 UTCGHSA enrichment
  25. 2026-09-11 15:30 UTCEG score recompute
Show 15 more
  1. 2026-09-11 15:30 UTCGHSA enrichment
  2. 2026-09-11 14:53 UTCEPSS rescore
  3. 2026-09-11 14:53 UTCEPSS rescore
  4. 2026-09-11 14:29 UTCEG score recompute
  5. 2026-09-11 14:29 UTCGHSA enrichment
  6. 2026-09-11 01:21 UTCGHSA enrichment
  7. 2026-09-10 12:13 UTCEG score recompute
  8. 2026-09-10 12:13 UTCGHSA enrichment
  9. 2026-09-09 23:05 UTCGHSA enrichment
  10. 2026-09-09 08:43 UTCGHSA enrichment
  11. 2026-09-08 19:35 UTCEG score recompute
  12. 2026-09-08 19:35 UTCGHSA enrichment
  13. 2026-09-08 18:34 UTCEG score recompute
  14. 2026-09-08 17:44 UTCEG score recompute
  15. 2026-09-08 17:44 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-81821?
CVE-2026-81821 is a high vulnerability published on September 8, 2026. The vulnerability, if exploited, could allow a miscreant with read access to PIMBoards project files to decrypt and view sensitive information.
When was CVE-2026-81821 disclosed?
CVE-2026-81821 was first published in the National Vulnerability Database on September 8, 2026, with the most recent update on September 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-81821 actively exploited?
CVE-2026-81821 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.8% of all scored CVEs.
What is the CVSS score of CVE-2026-81821?
CVE-2026-81821 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2026-81821?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-81821, 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-2026-81821

Explore →

Is Your Infrastructure Affected by CVE-2026-81821?

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

Start Free Scan →Browse All CVEs