CVE-2026-95526

HIGHPre-NVD 7.37.3
EchelonGraph scoreHIGH confidence

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

Score 7.3 from GitHub Security Advisory (severity: HIGH) published 2026-10-06. A secondary CVSS source baseline 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
7.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.3Exploit: None knownExposed services: Not assessed

Update the WordPress BEAR Plugin to the latest available version (at least 1.2.3) (from the CVE record's solution, Patchstack) — apply it.

Unauthenticated Broken Access Control in BEAR <= 1.2.2 versions.

CVSS v3
7.3
EG Score
7.3HIGHhigh confidence
EG Risk
48
EG Risk 48/100

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 (value × EchelonGraph’s weight)
Severity73% × 45%
The EG Score, 7.3 of 10.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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: Update the WordPress BEAR Plugin to the latest available version (at least 1.2.3) (from the CVE record's solution, Patchstack). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.2%
EPSS %ILE
12th
KEV
Not listed

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

Update the WordPress BEAR Plugin to the latest available version (at least 1.2.3) (from the CVE record's solution, Patchstack). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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

October 6, 2026

Last Modified

October 6, 2026

References (1)

Vendor Advisories for CVE-2026-95526(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 30× in last 7d / 38× 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.

  1. 2026-10-13 04:12 UTCEG score recompute
  2. 2026-10-13 04:12 UTCGHSA enrichmentGHSA-56vc-pjw6-c4x7 · GitHub severity HIGH · GitHub CVSS 7.3
  3. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  4. 2026-10-12 14:41 UTCEG score recompute
  5. 2026-10-11 19:11 UTCEG score recompute
  6. 2026-10-11 17:59 UTCGHSA enrichmentGHSA-56vc-pjw6-c4x7 · GitHub severity HIGH · GitHub CVSS 7.3
  7. 2026-10-11 16:27 UTCEG score recompute
  8. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  9. 2026-10-11 13:39 UTCEG score recompute
  10. 2026-10-11 06:51 UTCEG score recompute
  11. 2026-10-11 06:51 UTCGHSA enrichmentGHSA-56vc-pjw6-c4x7 · GitHub severity HIGH · GitHub CVSS 7.3
  12. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  13. 2026-10-10 19:43 UTCGHSA enrichmentGHSA-56vc-pjw6-c4x7 · GitHub severity HIGH · GitHub CVSS 7.3
  14. 2026-10-10 08:35 UTCGHSA enrichmentGHSA-56vc-pjw6-c4x7 · GitHub severity HIGH · GitHub CVSS 7.3
  15. 2026-10-09 21:26 UTCEG score recompute
  16. 2026-10-09 21:26 UTCGHSA enrichmentGHSA-56vc-pjw6-c4x7 · GitHub severity HIGH · GitHub CVSS 7.3
  17. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  18. 2026-10-09 10:17 UTCGHSA enrichmentGHSA-56vc-pjw6-c4x7 · GitHub severity HIGH · GitHub CVSS 7.3
  19. 2026-10-08 23:01 UTCEG score recompute
  20. 2026-10-08 23:01 UTCGHSA enrichmentGHSA-56vc-pjw6-c4x7 · GitHub severity HIGH · GitHub CVSS 7.3
  21. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  22. 2026-10-08 11:53 UTCGHSA enrichmentGHSA-56vc-pjw6-c4x7 · GitHub severity HIGH · GitHub CVSS 7.3
  23. 2026-10-08 00:44 UTCEG score recompute
  24. 2026-10-08 00:44 UTCGHSA enrichmentGHSA-56vc-pjw6-c4x7 · GitHub severity HIGH · GitHub CVSS 7.3
  25. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 12th percentile
Show 13 more
  1. 2026-10-07 13:35 UTCGHSA enrichmentGHSA-56vc-pjw6-c4x7 · GitHub severity HIGH · GitHub CVSS 7.3
  2. 2026-10-07 02:27 UTCGHSA enrichmentGHSA-56vc-pjw6-c4x7 · GitHub severity HIGH · GitHub CVSS 7.3
  3. 2026-10-06 15:19 UTCEG score recompute
  4. 2026-10-06 15:19 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  5. 2026-10-06 15:18 UTCGHSA enrichmentGHSA-56vc-pjw6-c4x7 · GitHub severity HIGH · GitHub CVSS 7.3
  6. 2026-10-06 11:27 UTCEG score recompute
  7. 2026-10-06 11:27 UTCGHSA enrichmentGHSA-56vc-pjw6-c4x7 · GitHub severity HIGH · GitHub CVSS 7.3
  8. 2026-10-06 10:45 UTCEG score recompute
  9. 2026-10-06 10:45 UTCGHSA enrichmentGHSA-56vc-pjw6-c4x7 · GitHub severity HIGH · GitHub CVSS 7.3
  10. 2026-10-06 09:56 UTCEG score recompute
  11. 2026-10-06 09:56 UTCGHSA enrichmentGHSA-56vc-pjw6-c4x7 · GitHub severity HIGH · GitHub CVSS 7.3
  12. 2026-10-06 08:52 UTCEG score recomputeFirst assessed: 7.3 HIGH
  13. 2026-10-06 08:52 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-95526?
CVE-2026-95526 is a high-severity vulnerability; its CVE record was published on October 6, 2026. Unauthenticated Broken Access Control in BEAR <= 1.2.2 versions.
When was the CVE record for CVE-2026-95526 published?
The CVE record for CVE-2026-95526 was published on October 6, 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 October 6, 2026; the record at its source may have been updated since.
Is CVE-2026-95526 actively exploited?
CVE-2026-95526 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (12th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-95526?
CVE-2026-95526 has a CVSS base score of 7.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-95526?
The CVE record's solution for CVE-2026-95526, written by its CNA Patchstack, names the fix: "Update the WordPress BEAR Plugin to the latest available version (at least 1.2.3)." The vendor advisories EchelonGraph has for CVE-2026-95526 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-95526?

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

Book a Demo →Browse All CVEs