Vulnerability in OSS file service URL fetch API (CVE-2026-42337)
Summary
Vulnerability in OSS file service URL fetch API (CVE-2026-42337). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.8.1 or later.
Original description
The description as published by the source.
MaxKB is an open-source AI assistant for enterprise. MaxKB 2.8.0 and prior are vulnerable to a broken access control vulnerability in the OSS file service URL fetch API (chat/api/oss/get_url). The endpoint uses application_id from the URL path without validating ownership, allowing attackers to perform operations under other applications’ policies. This vulnerability is fixed in 2.8.1.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-42337 has been found in OSS file service URL fetch API.
Risk of unauthorized operations or information disclosure.
What to do: upgrade OSS file service URL fetch API to 2.8.1 or later.
If unsure, ask your IT team or search "OSS file service URL fetch API CVE-2026-42337" on the vendor's site.
CVE-2026-42337 (OSS file service URL fetch API) — CWE-862
Patched: 2.8.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-862) exists in OSS file service URL fetch API.
Check the vendor advisory for the affected versions of OSS file service URL fetch API.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.8.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで OSS file service URL fetch API を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade OSS file service URL fetch API to 2.8.1ステージング環境で 2.8.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov