CVE-2026-44743

LOWPre-NVD 3.73.7
EchelonGraph scoreHIGH confidence

Score 3.7 from GitHub Security Advisory (severity: LOW) published 2026-06-09. the CNA's CVSS baseline 3.7; sources differ by 0.0.

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

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

Under certain conditions, when an unauthorized attacker accesses a specific endpoint, SAP Business Objects application leaks sensitive information .This has a low impact on the confidentiality of the data. There is no impact on integrity and availability of the application.

CVSS v3
3.7
EG Score
3.7(high)
EPSS
8.6%
KEV
Not listed

Published

June 9, 2026

Last Modified

June 9, 2026

Vendor Advisories for CVE-2026-44743(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 9× in last 7d / 51× 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 02:23 UTCEPSS rescore
  3. 2026-07-05 02:30 UTCEPSS rescore
  4. 2026-07-04 14:35 UTCEG score recompute
  5. 2026-07-04 14:35 UTCGHSA enrichment
  6. 2026-07-04 06:31 UTCEPSS rescore
  7. 2026-07-01 15:07 UTCEPSS rescore
  8. 2026-07-01 06:23 UTCEG score recompute
  9. 2026-07-01 06:23 UTCGHSA enrichment
  10. 2026-06-29 14:06 UTCEPSS rescore
  11. 2026-06-29 14:06 UTCEPSS rescore
  12. 2026-06-28 14:07 UTCEPSS rescore
  13. 2026-06-28 04:56 UTCEPSS rescore
  14. 2026-06-28 04:56 UTCEPSS rescore
  15. 2026-06-28 01:40 UTCEG score recompute
  16. 2026-06-28 01:40 UTCGHSA enrichment
  17. 2026-06-27 03:08 UTCEPSS rescore
  18. 2026-06-25 13:49 UTCEPSS rescore
  19. 2026-06-25 13:49 UTCEPSS rescore
  20. 2026-06-24 22:35 UTCEG score recompute
  21. 2026-06-24 22:34 UTCGHSA enrichment
  22. 2026-06-24 14:05 UTCEPSS rescore
  23. 2026-06-23 21:33 UTCEPSS rescore
  24. 2026-06-22 14:25 UTCEPSS rescore
  25. 2026-06-22 14:25 UTCEPSS rescore
Show 26 more
  1. 2026-06-21 19:36 UTCEG score recompute
  2. 2026-06-21 19:36 UTCGHSA enrichment
  3. 2026-06-21 14:56 UTCEPSS rescore
  4. 2026-06-21 14:56 UTCEPSS rescore
  5. 2026-06-21 01:59 UTCEPSS rescore
  6. 2026-06-19 19:25 UTCEPSS rescore
  7. 2026-06-18 17:52 UTCEPSS rescore
  8. 2026-06-18 17:52 UTCEPSS rescore
  9. 2026-06-18 10:11 UTCEG score recompute
  10. 2026-06-18 10:11 UTCGHSA enrichment
  11. 2026-06-17 17:53 UTCEPSS rescore
  12. 2026-06-16 17:52 UTCEPSS rescore
  13. 2026-06-15 17:49 UTCEPSS rescore
  14. 2026-06-15 07:13 UTCEG score recompute
  15. 2026-06-15 07:13 UTCGHSA enrichment
  16. 2026-06-13 23:00 UTCEPSS rescore
  17. 2026-06-12 23:12 UTCEPSS rescore
  18. 2026-06-12 23:12 UTCEPSS rescore
  19. 2026-06-12 04:14 UTCEG score recompute
  20. 2026-06-12 04:14 UTCGHSA enrichment
  21. 2026-06-11 14:00 UTCEPSS rescore
  22. 2026-06-10 22:18 UTCEPSS rescore
  23. 2026-06-10 13:22 UTCEPSS rescore
  24. 2026-06-10 13:22 UTCEPSS rescore
  25. 2026-06-09 01:16 UTCEG score recompute
  26. 2026-06-09 01:15 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-44743?
CVE-2026-44743 is a low vulnerability published on June 9, 2026. Under certain conditions, when an unauthorized attacker accesses a specific endpoint, SAP Business Objects application leaks sensitive information .This has a low impact on the confidentiality of the data. There is no impact on integrity and availability of the application.
When was CVE-2026-44743 disclosed?
CVE-2026-44743 was first published in the National Vulnerability Database on June 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44743 actively exploited?
CVE-2026-44743 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 8.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-44743?
CVE-2026-44743 has a CVSS v4.0 base score of 3.7 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-44743?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44743, 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-44743

Explore →

Is Your Infrastructure Affected by CVE-2026-44743?

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