CVE-2026-44957

MEDIUMPre-NVD 4.34.3
EchelonGraph scoreHIGH confidence

Score 4.3 from GitHub Security Advisory published 2026-06-23. a secondary CVSS source baseline 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
4.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.3Exploit: NoneExposed: 0

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

A missing access control check when invoking various modify methods in the XML‑RPC API of Revive Adserver 6.0.6 and earlier. The API allowed entities to be reassigned to different parent entities, leading to inconsistent ownership relationships. This issue was exploitable only in combination with CVE‑2026‑34917 or with third‑party API extensions that expose API functionality to low‑privileged users. Access control checks have been added to validate access to parent entities in the API modify methods.

CVSS v3
4.3
EG Score
4.3(high)
EPSS
14.5%
KEV
Not listed

Published

June 23, 2026

Last Modified

June 23, 2026

Advisory Details (1)

Auto-updated Jun 23, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-44957(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 / 41× 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-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 09:36 UTCEG score recompute
  3. 2026-07-06 09:36 UTCGHSA enrichment
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-05 10:10 UTCEG score recompute
  6. 2026-07-05 10:10 UTCGHSA enrichment
  7. 2026-07-05 02:30 UTCEPSS rescore
  8. 2026-07-04 10:48 UTCEG score recompute
  9. 2026-07-04 10:48 UTCGHSA enrichment
  10. 2026-07-03 11:25 UTCEG score recompute
  11. 2026-07-03 11:25 UTCGHSA enrichment
  12. 2026-07-02 12:00 UTCEG score recompute
  13. 2026-07-02 12:00 UTCGHSA enrichment
  14. 2026-07-01 15:07 UTCEPSS rescore
  15. 2026-07-01 12:37 UTCEG score recompute
  16. 2026-07-01 12:37 UTCGHSA enrichment
  17. 2026-06-30 23:22 UTCEPSS rescore
  18. 2026-06-30 13:15 UTCEG score recompute
  19. 2026-06-30 13:15 UTCGHSA enrichment
  20. 2026-06-29 14:06 UTCEPSS rescore
  21. 2026-06-29 14:06 UTCEPSS rescore
  22. 2026-06-29 13:52 UTCEG score recompute
  23. 2026-06-29 13:52 UTCGHSA enrichment
  24. 2026-06-28 14:30 UTCEG score recompute
  25. 2026-06-28 14:30 UTCGHSA enrichment
Show 16 more
  1. 2026-06-28 14:07 UTCEPSS rescore
  2. 2026-06-28 04:56 UTCEPSS rescore
  3. 2026-06-28 04:56 UTCEPSS rescore
  4. 2026-06-27 15:08 UTCEG score recompute
  5. 2026-06-27 15:08 UTCGHSA enrichment
  6. 2026-06-27 03:08 UTCEPSS rescore
  7. 2026-06-26 15:45 UTCEG score recompute
  8. 2026-06-26 15:45 UTCGHSA enrichment
  9. 2026-06-25 16:20 UTCEG score recompute
  10. 2026-06-25 16:20 UTCGHSA enrichment
  11. 2026-06-25 13:49 UTCEPSS rescore
  12. 2026-06-24 16:58 UTCEG score recompute
  13. 2026-06-24 16:58 UTCGHSA enrichment
  14. 2026-06-24 14:05 UTCEPSS rescore
  15. 2026-06-23 17:35 UTCEG score recompute
  16. 2026-06-23 17:34 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-44957?
CVE-2026-44957 is a medium vulnerability published on June 23, 2026. A missing access control check when invoking various modify methods in the XML‑RPC API of Revive Adserver 6.0.6 and earlier. The API allowed entities to be reassigned to different parent entities, leading to inconsistent ownership relationships. This issue was exploitable only in combination with…
When was CVE-2026-44957 disclosed?
CVE-2026-44957 was first published in the National Vulnerability Database on June 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44957 actively exploited?
CVE-2026-44957 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 14.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-44957?
CVE-2026-44957 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-44957?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44957, 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-44957

Explore →

Is Your Infrastructure Affected by CVE-2026-44957?

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