SSRF (Server-Side Request Forgery) in org.apache.fesod:fesod-sheet (CVE-2026-49328)
Summary
SSRF in org.apache.fesod:fesod-sheet (CVE-2026-49328). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.0.2-incubating or later.
Original description
The description as published by the source.
Server-Side Request Forgery (SSRF) in the UrlImageConverter component of Apache Fesod (Incubating) fesod-sheet before 2.0.2-incubating allows attackers to cause outbound network requests to internal or otherwise restricted resources via a user-supplied image URL. Users are recommended to upgrade to version 2.0.2-incubating, which fixes this issue.
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-49328 has been found in org.apache.fesod:fesod-sheet.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade org.apache.fesod:fesod-sheet to 2.0.2-incubating or later.
If unsure, ask your IT team or search "org.apache.fesod:fesod-sheet CVE-2026-49328" on the vendor's site.
CVE-2026-49328 (org.apache.fesod:fesod-sheet) — CWE-918 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.0.2-incubating — 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.
SSRF (CWE-918) exists in org.apache.fesod:fesod-sheet.
Check the vendor advisory for the affected versions of org.apache.fesod:fesod-sheet.
Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.
Update to 2.0.2-incubating.
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・依存マニフェストで org.apache.fesod:fesod-sheet を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.apache.fesod:fesod-sheet to 2.0.2-incubatingステージング環境で 2.0.2-incubating に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory lists.apache.org
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web fesod.apache.org
- web github.com
- web openwall.com
- web repo.maven.apache.org