CVE-2025-48950

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 70% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: Elevated riskExposed: 0

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

MaxKB is an open-source AI assistant for enterprise. Prior to version 1.10.8-lts, Sandbox only restricts the execution permissions of binary files in common directories, such as /bin,/usr/bin, etc. Therefore, attackers can exploit some files with execution permissions in non blacklisted directories to carry out attacks. Version 1.10.8-lts fixes the issue.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
56(Track)
EG Risk 56/100SSVC: Track

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
Severity88% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
38%
KEV
Not listed

Published

June 3, 2025

Last Modified

August 6, 2025

Advisory Details (4)

Auto-updated Aug 26, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available🟡 PoC Available

Python Sandbox Bypass in Function Library · Advisory · 1Panel-dev/MaxKB · GitHub

https://github.com/1Panel-dev/MaxKB/security/advisories/GHSA-p2qq-x9j2-px8v
github_release Patch Available

v1.10.8-lts

Patch available: 1Panel-dev/MaxKB v1.10.8-lts

https://github.com/1Panel-dev/MaxKB/releases/tag/v1.10.8-lts
github_pr Patch Available

build: Sensitive directory permissions

Patch available: 1Panel-dev/MaxKB v1.10.11-lts (PR #3127 merged 2025-05-21)

https://github.com/1Panel-dev/MaxKB/pull/3127
github_commit Patch Available

commit 187e9c1e4ea1 (1Panel-dev/MaxKB)

Patch available: 1Panel-dev/MaxKB v1.10.11-lts (contains commit 187e9c1e4ea1)

https://github.com/1Panel-dev/MaxKB/commit/187e9c1e4ea1ebb6864c5bf61558c42f2fc6c005

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 32× 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.

Showing the most recent 100 of 156 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-48950?
CVE-2025-48950 is a high vulnerability published on June 3, 2025. MaxKB is an open-source AI assistant for enterprise. Prior to version 1.10.8-lts, Sandbox only restricts the execution permissions of binary files in common directories, such as /bin,/usr/bin, etc. Therefore, attackers can exploit some files with execution permissions in non blacklisted directories…
When was CVE-2025-48950 disclosed?
CVE-2025-48950 was first published in the National Vulnerability Database on June 3, 2025, with the most recent update on August 6, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-48950 actively exploited?
CVE-2025-48950 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 61.8% of all scored CVEs.
What is the CVSS score of CVE-2025-48950?
CVE-2025-48950 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2025-48950?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-48950, 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-2025-48950

Explore →

Is Your Infrastructure Affected by CVE-2025-48950?

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

Start Free Scan →Browse All CVEs