Skip to main content
CVE-2026-67615VulnerabilityPublished Updated

openEQUELLA before 2026.1.0 contains an authenticated remote code execution vulnerability that allows any

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-67615· High 8.7

Not known to be exploited · CVSS 8.7 High : upgrade to 2026.1.0 soon.

Data as of 29 Oct 2026, 16:36 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.7
CNA (VulnCheck)CVSS 3.18.8
Patch
Available – fixed in 2026.1.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 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 29 Oct 2026.

What to do

Upgrade openEQUELLA to 2026.1.0.

Affected software

ProductAffectedFixed in
Apereo FoundationopenEQUELLAAffected
  • <2026.1.0
Fixed in
  • 2026.1.0
GitHubopenEQUELLApkg:github/openEQUELLAOther threatsAffected
  • <2026.1.0
Fixed in
  • 2026.1.0

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

AI-suggested

A fix is available in openEQUELLA version 2026.1.0. Users should upgrade to this version or later to remediate the vulnerability. No other mitigation or workaround is indicated in the provided data.

Description

openEQUELLA versions prior to 2026.1.0 have an authenticated remote code execution vulnerability. This flaw allows any authenticated non-guest user to execute arbitrary code by exploiting Java deserialization in the HTTP invoker endpoint. The vulnerability arises because attackers can bypass the class-name denylist by nesting a serialized payload inside a java.security.SignedObject, which is deserialized by a separate ObjectInputStream without denylist enforcement, ultimately triggering a JNDI sink that enables code execution.

References

Community reviews

Loading reviews…