← Back
CVE-2026-49832
Code Injection in org.dspace:dspace-api (CVE-2026-49832)
Summary
code injection in org.dspace:dspace-api (CVE-2026-49832). Risk of unauthorized operations or information disclosure. Exploitable via ``dspace.cfg``. Mitigation: upgrade to `10.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-49832** has been found in org.dspace:dspace-api.
Attackers can target a specific entry point like ``dspace.cfg`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade org.dspace:dspace-api to **10.0** or later.
If unsure, ask your IT team or search "org.dspace:dspace-api CVE-2026-49832" on the vendor's site.
CVE-2026-49832 (org.dspace:dspace-api) — CWE-94 /
Attack surface: `dspace.cfg` / `local.cfg`
Patched: `10.0` — apply immediately
Workaround: set ldn.: enabled
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.
❓ What is the problem
**arbitrary code execution** (CWE-94) exists in org.dspace:dspace-api. Attackers reach the vulnerable code path via ``dspace.cfg`` without authentication.
📍 Affected scope
org.dspace:dspace-api — . Attack surface: `dspace.cfg` / `local.cfg`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **10.0**.
🛡️ Workaround
Workaround: set ldn.: enabled
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'org.dspace:dspace-api' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'org.dspace:dspace-api' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `org.dspace:dspace-api` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
set ldn.: enabledパッチが適用されるまでの応急処置として、set ldn.: enabled を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade org.dspace:dspace-api to 10.0ステージング環境で 10.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
org.dspace:dspace-api
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10.0"}]}]