← Back
CVE-2026-73644 critical CVSS 9.6

Vulnerability in org.openidentityplatform.opendj:opendj-server-legacy (CVE-2026-73644)

Summary

vulnerability in org.openidentityplatform.opendj:opendj-server-legacy (CVE-2026-73644). Confidential information can be exposed externally. Mitigation: upgrade to `5.1.2` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-73644** has been found in org.openidentityplatform.opendj:opendj-server-legacy. Confidential information can be exposed externally. CVSS score: 9.6/10. What to do: upgrade org.openidentityplatform.opendj:opendj-server-legacy to **5.1.2** or later. If unsure, ask your IT team or search "org.openidentityplatform.opendj:opendj-server-legacy CVE-2026-73644" on the vendor's site.
CVE-2026-73644 (org.openidentityplatform.opendj:opendj-server-legacy) — CWE-285 / CVSS v3 9.6 Attack vector: remote (network-reachable) / no user interaction Patched: `5.1.2` — apply immediately Workaround: Restrict or revoke the proxied-auth privilege until upgraded. 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
**A vulnerability** (CWE-285) exists in org.openidentityplatform.opendj:opendj-server-legacy.
📍 Affected scope
org.openidentityplatform.opendj:opendj-server-legacy — .
🔥 Severity
Severity: Critical (CVSS 9.6/10). Confidential information can be exposed externally
🔧 How to fix
Update to **5.1.2**.
🛡️ Workaround
Workaround: Restrict or revoke the proxied-auth privilege until upgraded.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'org.openidentityplatform.opendj:opendj-server-legacy' .` 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

  1. 1
    Identify exposure identify
    grep -r 'org.openidentityplatform.opendj:opendj-server-legacy' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `org.openidentityplatform.opendj:opendj-server-legacy` を grep し、稼働しているサービス・バージョンを把握する。

  2. 5
    Apply temporary workaround mitigate
    Restrict or revoke the proxied-auth privilege until upgraded.

    パッチが適用されるまでの応急処置として、Restrict or revoke the proxied-auth privilege until upgraded. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 6
    Apply patch patch
    Upgrade org.openidentityplatform.opendj:opendj-server-legacy to 5.1.2

    ステージング環境で 5.1.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  4. 7
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

maven org.openidentityplatform.opendj:opendj-server-legacy
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.1.2"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →