Skip to main content
VulnerabilityPublished

CVE-2026-68536: Server-Side Request Forgery / Local File Inclusion in Apache MyFace Core

Affects coreSource GCVE Database

0
Compare
Authoritative record:CVE-2026-68536· Critical 9.8

Not known to be exploited · CVSS 9.8 Critical · fixed in 4.1.4 : patch core as a priority.

Data as of 31 Oct 2026, 08:20 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.1.4, 4.0.4, 3.0.4 +1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 16 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade org.apache.myfaces/core to 4.1.4, 4.0.4, 3.0.4 or 2.3.12.

Affected software

ProductAffectedFixed in
Mavenorg.apache.myfaces/corepkg:maven/org.apache.myfaces/coreOther threatsAffected
  • <2.3.12
  • <3.0.4
  • <4.0.4
  • <4.1.4
Fixed in
  • 2.3.12
  • 3.0.4
  • 4.0.4
  • 4.1.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade to one of the fixed versions: 2.3.12, 2.3-next-M9, 3.0.4, 4.0.4, or 4.1.4. No other mitigation guidance is provided.

Description

Server-Side Request Forgery / Local File Inclusion in Apache MyFace Core. Older unsupported versions may also be affected. Users are recommended to upgrade to versions 2.3.12, 2.3-next-M9, 3.0.4, 4.0.4, or 4.1.4, which fix this issue.

References

Community reviews

Loading reviews…