CVE-2026-6881

CRITICALPre-NVD 9.49.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (26th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week
9.4EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 9.4Exploit: None knownExposed services: Not assessed

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

A SQL Injection in the Giving Reports functionality in Ellucian Advance Web and Legacy Advance allows an authenticated attacker to extract sensitive information from databases via a crafted SQL query in the class credit field.

This issue affects Advance Web: all versions; Legacy Advance: all versions.

Ellucian CRM Advance is not impacted.

CVSS v3
9.4
EG Score
9.4CRITICALmedium confidence
EG Risk
42
EG Risk 42/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity94% × 45%
Impact severity (EG Severity): CVSS 9.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
26th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.4): severity, escalated by confirmed exploitation. This CVE's 9.4 is its impact severity (EG Severity), not escalated.

EG Severity
9.4 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-18). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 28, 2026

Last Modified

September 9, 2026

Advisory Details (1)

Auto-updated Oct 2, 2026
No fix on record yet.
Web page

Advisory: Ellucian Advance :: SRA Labs | Cybersecurity Research & Innovation by Security Risk Advisors

https://labs.sra.io/posts/ellucian

Vendor Advisories for CVE-2026-6881(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 / 81× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 421 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 321 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  2. 2026-10-19 15:04 UTCEG score recompute
  3. 2026-10-19 15:04 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  4. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  5. 2026-10-18 12:51 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  6. 2026-10-18 03:19 UTCEG score recompute
  7. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  8. 2026-10-17 10:38 UTCEG score recompute
  9. 2026-10-17 10:38 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  10. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  11. 2026-10-16 08:25 UTCEG score recompute
  12. 2026-10-16 08:25 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  13. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  14. 2026-10-15 06:11 UTCEG score recompute
  15. 2026-10-15 06:10 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  16. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  17. 2026-10-14 01:47 UTCEG score recompute
  18. 2026-10-14 01:47 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  19. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  20. 2026-10-12 21:58 UTCEG score recompute
  21. 2026-10-12 21:58 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  22. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  23. 2026-10-12 15:44 UTCEG score recompute
  24. 2026-10-12 05:57 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  25. 2026-10-11 19:30 UTCEG score recompute
Show 75 more
  1. 2026-10-11 16:45 UTCEG score recompute
  2. 2026-10-11 14:06 UTCEG score recompute
  3. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  4. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  5. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  6. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  7. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  8. 2026-10-07 04:14 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  9. 2026-10-07 00:05 UTCEG score recompute
  10. 2026-10-07 00:05 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  11. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  12. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  13. 2026-10-05 02:42 UTCEG score recompute
  14. 2026-10-05 02:42 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  15. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  16. 2026-10-04 12:36 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  17. 2026-10-04 07:08 UTCEG score recompute
  18. 2026-10-04 07:08 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  19. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  20. 2026-10-03 03:12 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  21. 2026-10-02 18:23 UTCEG score recompute
  22. 2026-10-02 18:23 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  23. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  24. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  25. 2026-10-01 16:12 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  26. 2026-10-01 12:12 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  27. 2026-10-01 07:42 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  28. 2026-10-01 03:42 UTCEG score recompute
  29. 2026-10-01 03:42 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  30. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  31. 2026-09-29 07:42 UTCEG score recompute
  32. 2026-09-29 07:42 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  33. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  34. 2026-09-28 12:56 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  35. 2026-09-28 07:23 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  36. 2026-09-28 03:22 UTCEG score recompute
  37. 2026-09-28 03:22 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  38. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  39. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  40. 2026-09-25 10:08 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  41. 2026-09-25 06:08 UTCEG score recompute
  42. 2026-09-25 06:08 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  43. 2026-09-24 10:16 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  44. 2026-09-24 06:16 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  45. 2026-09-24 01:54 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  46. 2026-09-23 21:54 UTCEG score recompute
  47. 2026-09-23 21:54 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  48. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  49. 2026-09-23 09:40 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  50. 2026-09-23 05:39 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  51. 2026-09-23 01:40 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  52. 2026-09-22 21:40 UTCEG score recompute
  53. 2026-09-22 21:40 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  54. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  55. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  56. 2026-09-20 11:17 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  57. 2026-09-20 04:32 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  58. 2026-09-20 00:31 UTCEG score recompute
  59. 2026-09-20 00:31 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  60. 2026-09-19 05:16 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  61. 2026-09-18 22:26 UTCEG score recompute
  62. 2026-09-18 22:26 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  63. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  64. 2026-09-18 17:55 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  65. 2026-09-18 09:57 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  66. 2026-09-18 05:57 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  67. 2026-09-18 01:57 UTCEG score recompute
  68. 2026-09-18 01:57 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  69. 2026-09-17 09:00 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  70. 2026-09-17 01:40 UTCEG score recompute
  71. 2026-09-17 01:40 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  72. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  73. 2026-09-16 11:50 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL
  74. 2026-09-16 05:52 UTCEG score recompute
  75. 2026-09-16 05:52 UTCGHSA enrichmentGHSA-xfrq-3339-mcj4 · GitHub severity CRITICAL

Frequently asked(5)

What is CVE-2026-6881?
CVE-2026-6881 is a critical-severity vulnerability; its CVE record was published on July 28, 2026. A SQL Injection in the Giving Reports functionality in Ellucian Advance Web and Legacy Advance allows an authenticated attacker to extract sensitive information from databases via a crafted SQL query in the class credit field. This issue affects Advance Web: all versions; Legacy Advance: all…
When was the CVE record for CVE-2026-6881 published?
The CVE record for CVE-2026-6881 was published on July 28, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-6881 actively exploited?
CVE-2026-6881 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (26th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-6881?
CVE-2026-6881 has a CVSS base score of 9.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-6881?
No fix for CVE-2026-6881 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-6881 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-6881

Explore →

Is Your Infrastructure Affected by CVE-2026-6881?

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