CVE-2026-81823

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory published 2026-09-08. a secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: 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 an unauthenticated miscreant to perform read operations intended only for PIMBoards users, resulting in information disclosure. Write operations are not impacted.

CVSS v3
5.3
EG Score
5.3(high)
EG Risk
39(Track)
EG Risk 39/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
Severity53% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
30%
KEV
Not listed

Published

September 8, 2026

Last Modified

September 14, 2026

Advisory Details (1)

Auto-updated Sep 9, 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-81823(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 19× in last 7d / 52× 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-24 19:30 UTCEG score recompute
  2. 2026-09-24 19:30 UTCGHSA enrichment
  3. 2026-09-24 14:04 UTCEPSS rescore
  4. 2026-09-23 19:41 UTCEG score recompute
  5. 2026-09-23 19:41 UTCGHSA enrichment
  6. 2026-09-23 17:54 UTCEPSS rescore
  7. 2026-09-22 19:30 UTCEG score recompute
  8. 2026-09-22 19:30 UTCGHSA enrichment
  9. 2026-09-22 16:01 UTCEPSS rescore
  10. 2026-09-21 21:09 UTCEPSS rescore
  11. 2026-09-21 19:41 UTCEG score recompute
  12. 2026-09-21 19:41 UTCGHSA enrichment
  13. 2026-09-20 20:16 UTCEPSS rescore
  14. 2026-09-20 19:52 UTCGHSA enrichment
  15. 2026-09-19 20:03 UTCEG score recompute
  16. 2026-09-19 20:03 UTCGHSA enrichment
  17. 2026-09-18 20:15 UTCEG score recompute
  18. 2026-09-18 20:15 UTCGHSA enrichment
  19. 2026-09-18 19:28 UTCEPSS rescore
  20. 2026-09-17 20:19 UTCEG score recompute
  21. 2026-09-17 20:19 UTCGHSA enrichment
  22. 2026-09-16 19:00 UTCEG score recompute
  23. 2026-09-16 19:00 UTCGHSA enrichment
  24. 2026-09-16 14:08 UTCEPSS rescore
  25. 2026-09-16 05:15 UTCEPSS rescore
Show 27 more
  1. 2026-09-15 19:11 UTCEG score recompute
  2. 2026-09-15 19:11 UTCGHSA enrichment
  3. 2026-09-15 03:12 UTCEPSS rescore
  4. 2026-09-15 03:12 UTCEPSS rescore
  5. 2026-09-14 19:22 UTCEG score recompute
  6. 2026-09-14 19:22 UTCGHSA enrichment
  7. 2026-09-14 19:05 UTCEG score recompute
  8. 2026-09-14 19:05 UTCGHSA enrichment
  9. 2026-09-14 15:00 UTCEG score recompute
  10. 2026-09-14 15:00 UTCGHSA enrichment
  11. 2026-09-13 15:10 UTCGHSA enrichment
  12. 2026-09-12 15:19 UTCEG score recompute
  13. 2026-09-12 15:19 UTCGHSA enrichment
  14. 2026-09-11 15:30 UTCEG score recompute
  15. 2026-09-11 15:30 UTCGHSA enrichment
  16. 2026-09-11 14:53 UTCEPSS rescore
  17. 2026-09-11 14:53 UTCEPSS rescore
  18. 2026-09-11 14:35 UTCEG score recompute
  19. 2026-09-11 14:35 UTCGHSA enrichment
  20. 2026-09-10 19:13 UTCEG score recompute
  21. 2026-09-10 19:13 UTCGHSA enrichment
  22. 2026-09-09 19:24 UTCGHSA enrichment
  23. 2026-09-08 19:35 UTCEG score recompute
  24. 2026-09-08 19:35 UTCGHSA enrichment
  25. 2026-09-08 18:33 UTCEG score recompute
  26. 2026-09-08 17:42 UTCEG score recompute
  27. 2026-09-08 17:40 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-81823?
CVE-2026-81823 is a medium vulnerability published on September 8, 2026. The vulnerability, if exploited, could allow an unauthenticated miscreant to perform read operations intended only for PIMBoards users, resulting in information disclosure. Write operations are not impacted.
When was CVE-2026-81823 disclosed?
CVE-2026-81823 was first published in the National Vulnerability Database on September 8, 2026, with the most recent update on September 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-81823 actively exploited?
CVE-2026-81823 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 70.4% of all scored CVEs.
What is the CVSS score of CVE-2026-81823?
CVE-2026-81823 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-81823?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-81823, 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-81823

Explore →

Is Your Infrastructure Affected by CVE-2026-81823?

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

Book a Demo →Browse All CVEs