← Back
CVE-2026-44242
low
CVSS 3.7
Vulnerability in io.micronaut:micronaut-inject (CVE-2026-44242)
Summary
vulnerability in io.micronaut:micronaut-inject (CVE-2026-44242). Risk of unauthorized operations or information disclosure. Exploitable via ``ResourceBundleMessageSource``. Mitigation: upgrade to `4.10.22` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-44242** has been found in io.micronaut:micronaut-inject.
Attackers can target a specific entry point like ``ResourceBundleMessageSource`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.7/10.
What to do: upgrade io.micronaut:micronaut-inject to **4.10.22** or later.
If unsure, ask your IT team or search "io.micronaut:micronaut-inject CVE-2026-44242" on the vendor's site.
CVE-2026-44242 (io.micronaut:micronaut-inject) — CWE-400 / CVSS v3 3.7
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `ResourceBundleMessageSource` / `messageCache` / `ConcurrentLinkedHashMap` / `bundleCache`
Patched: `4.10.22` — 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.
❓ What is the problem
**A vulnerability** (CWE-400) exists in io.micronaut:micronaut-inject. Attackers reach the vulnerable code path via ``ResourceBundleMessageSource`` without authentication.
📍 Affected scope
io.micronaut:micronaut-inject — . Attack surface: `ResourceBundleMessageSource` / `messageCache` / `ConcurrentLinkedHashMap` / `bundleCache`.
🔥 Severity
Severity: Low (CVSS 3.7/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **4.10.22**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'io.micronaut:micronaut-inject' .` 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 'io.micronaut:micronaut-inject' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `io.micronaut:micronaut-inject` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade io.micronaut:micronaut-inject to 4.10.22ステージング環境で 4.10.22 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
io.micronaut:micronaut-inject
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.10.22"}]}]