Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-68536 – SSRF / Local File Inclusion – Apache MyFaces (JavaServer Faces implementation) mult

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-68536 is a critical Server-Side Request Forgery (SSRF) and Local File Inclusion (LFI) vulnerability (CWE-918) in Apache MyFaces Core, the Apache Software Foundation’s implementation of the JavaServer Faces (JSF) specification. The flaw allows an unauthenticated, remote attacker to make the server issue requests to arbitrary internal or external resources, or read local files, with no user interaction required. It carries a CVSS v3.1 base score of 9.8 (Critical).

Technical details

  • Root cause: A component of Apache MyFaces Core processes a request in a way that allows attacker-controlled input to be used to fetch remote resources (SSRF) or local files (LFI) on the server’s behalf.
  • Trigger conditions: Exploitation requires no authentication and no user interaction; the underlying weakness is triggered directly over the network against an exposed MyFaces application.
  • Attack vector: Network (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N).
  • Impact: Full compromise of confidentiality, integrity, and availability (C:H/I:H/A:H) is possible — an attacker could pivot to internal-only services via SSRF, read sensitive local files via LFI, or otherwise fully compromise the affected application/host.

Affected software

  • Apache MyFaces Core (org.apache.myfaces.core:myfaces-impl):
    • 2.2.0-beta through 2.2.15
    • 2.3.0
    • 2.3.1 up to (but not including) 2.3.12
    • 2.3-next-M1 up to (but not including) 2.3-next-M9
    • 3.0.0 up to (but not including) 3.0.4
    • 4.0.0 up to (but not including) 4.0.4
    • 4.1.0 up to (but not including) 4.1.4
  • Older, unsupported versions may also be affected.

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade Apache MyFaces Core to one of the fixed releases: 2.3.12, 2.3-next-M9, 3.0.4, 4.0.4, or 4.1.4, depending on the release line in use.
  • If no patch can be applied immediately: Restrict or monitor outbound network access from the application server to limit the impact of SSRF, and restrict filesystem read permissions available to the application process to reduce LFI exposure. Apply network-level controls (WAF/reverse proxy filtering) as a temporary compensating control until the upgrade can be completed, and prioritize patching internet-exposed instances first.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge