CVE-2026-129428

MEDIUMPre-NVD 5.45.4
EchelonGraph scoreHIGH confidence

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

Score 5.4 from GitHub Security Advisory (severity: MODERATE) published 2026-11-14. A secondary CVSS source baseline 5.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-125903 (ENISA EUVD) · GHSA-c2gc-chxg-hvqr (GitHub Security Advisories)Source: ENISA EUVD

5.4EG
EchelonGraph verdictPlan mitigationNo release containing the referenced fix is confirmed: check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.4Exploit: No code on recordExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

Pulse from 5.0.17 before 6.8.0 contains a missing authorization vulnerability in the /api/ai/approvals endpoints that allows authenticated viewer-level users to manage approval requests. Attackers can list pending requests to expose proposed commands and targets, and approve or deny other users' requests, altering decision and audit state.

CVSS v3
5.4
EG Score
5.4MEDIUMhigh confidence
EG Risk
40
EG Risk 40/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)
Severity54% × 45%
Impact severity (EG Severity): CVSS 5.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
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 public PoC (CISA Vulnrichment) · Automatable no (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: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.
EPSS PROB
0.3%
EPSS %ILE
18th
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 (5.4): severity, escalated by confirmed exploitation. This CVE's 5.4 is its impact severity (EG Severity), not escalated.

EG Severity
5.4 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS. 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: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.Each input and its source, and whom BOD 26-04 binds: 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).

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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

November 14, 2026

Last Modified

November 18, 2026

Advisory Details (6)

Auto-updated Nov 14, 2026
🔬 Proof of concept available. Fix referenced — no release confirmed yet. Sources: github, github_commit, github_pr.
Web page

Pulse 5.0.17 before 6.8.0 Missing Authorization via AI Assistant Approval API | Advisories | VulnCheck

https://www.vulncheck.com/advisories/pulse-5.0.17-before-6.8.0-missing-authorization-via-ai-assistant-approval-api
Web page

GitHub - rcourtman/Pulse: Real-time monitoring dashboard for Proxmox VE, PBS, Docker, Kubernetes, TrueNAS and vSphere. Self-hosted, with alerts for failed backups, full disks, unhealthy containers and offline nodes. · GitHub

https://github.com/rcourtman/Pulse
Web page

Pulse/internal/api/ai_handlers.go at v6.7.0 · rcourtman/Pulse · GitHub

https://github.com/rcourtman/Pulse/blob/v6.7.0/internal/api/ai_handlers.go#L7686
GitHub commit

commit f05119d97ea3 (rcourtman/Pulse)

Fix landed in rcourtman/Pulse commit f05119d97ea3 — awaiting tagged release

https://github.com/rcourtman/Pulse/commit/f05119d97ea3bc1980886d8c62dda7ce8fd39d4e
GitHub pull request

Use canonical session review authority for AI approvals

Fix merged in rcourtman/Pulse PR #4127 on 2026-11-08 — awaiting tagged release

https://github.com/rcourtman/Pulse/pull/4127
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Missing authorization lets authenticated viewers read and decide Pulse Assistant approvals · Advisory · rcourtman/Pulse · GitHub

Affected: v6.8.0 (first fixed prerelease v6.8.0-rc.2) by

https://github.com/rcourtman/Pulse/security/advisories/GHSA-9vxw-m79f-gxxr

Vendor Advisories for CVE-2026-129428(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 10× in last 7d / 14× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  2. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  3. 2026-11-20 05:42 UTCEchelonGraph re-scored
  4. 2026-11-20 05:42 UTCGHSA enrichmentGHSA-c2gc-chxg-hvqr · GitHub severity MODERATE · GitHub CVSS 5.4
  5. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  6. 2026-11-18 16:34 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  7. 2026-11-18 14:42 UTCEchelonGraph re-scored
  8. 2026-11-18 14:42 UTCGHSA enrichmentGHSA-c2gc-chxg-hvqr · GitHub severity MODERATE · GitHub CVSS 5.4
  9. 2026-11-18 14:29 UTCEchelonGraph re-scored
  10. 2026-11-18 14:29 UTCGHSA enrichmentGHSA-c2gc-chxg-hvqr · GitHub severity MODERATE · GitHub CVSS 5.4
  11. 2026-11-18 13:48 UTCEchelonGraph re-scored
  12. 2026-11-18 13:48 UTCGHSA enrichmentGHSA-c2gc-chxg-hvqr · GitHub severity MODERATE · GitHub CVSS 5.4
  13. 2026-11-17 16:34 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  14. 2026-11-16 16:49 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  15. 2026-11-15 16:57 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  16. 2026-11-14 15:47 UTCEchelonGraph re-scored
  17. 2026-11-14 15:47 UTCGHSA enrichmentGHSA-c2gc-chxg-hvqr · GitHub severity MODERATE · GitHub CVSS 5.4
  18. 2026-11-14 13:28 UTCEchelonGraph re-scored
  19. 2026-11-14 13:02 UTCENISA EUVD ID recordedEUVD-2026-125903 · Source: ENISA EUVD
  20. 2026-11-14 12:46 UTCEchelonGraph re-scoredFirst assessed: 5.4 MEDIUM
  21. 2026-11-14 12:39 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-129428?
CVE-2026-129428 is a medium-severity vulnerability; its CVE record was published on November 14, 2026. Pulse from 5.0.17 before 6.8.0 contains a missing authorization vulnerability in the /api/ai/approvals endpoints that allows authenticated viewer-level users to manage approval requests. Attackers can list pending requests to expose proposed commands and targets, and approve or deny other users'…
When was CVE-2026-129428 made public?
CVE-2026-129428 was made public on November 13, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on November 14, 2026. EchelonGraph's copy of the record carries a last-modified date of November 18, 2026; the record at its source may have been updated since.
Is CVE-2026-129428 actively exploited?
CVE-2026-129428 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (18th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-129428?
CVE-2026-129428 has a CVSS base score of 5.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-129428?
A fix for CVE-2026-129428 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2026-129428 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-129428?

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