How severe is CVE-2020-26234?

CVE-2020-26234 has a CVSS score of 4.8/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2020-26234?

CVE-2020-26234 affects the following packages: org.opencastproject:opencast-kernel (Maven), org.opencastproject:opencast-kernel (Maven). Ecosystems affected: Maven.

How do I fix CVE-2020-26234?

Update org.opencastproject:opencast-kernel to 7.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-26234 is resolved across your whole dependency graph.

How do I detect CVE-2020-26234 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.opencastproject:opencast-kernel, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2020-26234 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2020-26234 actively exploited in the wild?

No public exploit code has been indexed for CVE-2020-26234 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2020-26234?

CVE-2020-26234 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 20th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2020-26234?

CVE-2020-26234 is classified as CWE-346 (CWE-346). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2020-26234 published, and has it been updated?

CVE-2020-26234 was published on December 8, 2020 and was last updated on October 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2020-26234 — opencast-kernel

MEDIUMFix: opencast/opencast@4225bf9

CVE-2020-26234 is a medium-severity (CVSS 4.8) CWE-346 vulnerability in org.opencastproject:opencast-kernel. A fix is available for org.opencastproject:opencast-kernel — see the affected versions and patch details below.

Disabled Hostname Verification in Opencast

Also known asGHSA-44cw-p2hm-gpf6

Published

Dec 8, 2020

Updated

Oct 20, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Oct 31, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs20th percentile — riskier than 20% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

☕org.opencastproject:opencast-kernel☕org.opencastproject:opencast-kernel

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Opencast before version 8.9 and 7.9 disables HTTPS hostname verification of its HTTP client used for a large portion of Opencast's HTTP requests.

Hostname verification is an important part when using HTTPS to ensure that the presented certificate is valid for the host. Disabling it can allow for man-in-the-middle attacks.

Patches

This problem is fixed in Opencast 7.9 and Opencast 8.9

Self-Signed Certificates

Please be aware that fixing the problem means that Opencast will not simply accept any self-signed certificates any longer without properly importing them. If you need those, please make sure to import them into the Java key store. Better yet, get a valid certificate e.g. from Let's Encrypt.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.opencastproject:opencast-kernel`	all versions	7.9`org.opencastproject:opencast-kernel:7.9`
☕Maven	`org.opencastproject:opencast-kernel`	≥ 8.0&&< 8.9	8.9`org.opencastproject:opencast-kernel:8.9`

Affected Products

1 product · 2 configurations

Application

opencastapereo

≥ 8.0 && < 8.9

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.opencastproject:opencast-kernel, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.opencastproject:opencast-kernel to 7.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-26234 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Opencast before version 8.9 and 7.9 disables HTTPS hostname verification of its HTTP client used for a large portion of Opencast's HTTP requests. Hostname verification is an important part when using HTTPS to ensure that the presented certificate is valid for the host. Disabling it can allow for man-in-the-middle attacks. ### Patches This problem is fixed in Opencast 7.9 and Opencast 8.9 ### Self-Signed Certificates Please be aware that fixing the problem means that Opencast will not simply accept any self-signed certificates any longer without properly importing them. If you need those,

O3 Security · Impact-Aware SCA

Is CVE-2020-26234 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

4.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

High

Privileges Required

Low

User Interaction

Required

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:H/A:N

CWE Classification

CWE-346CWE-346

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

OpenSSF Scorecard

Package health score

opencast

4.9/10

Maintained10/10

Code-Review3/10

Branch-ProtectionN/A

Assessed Oct 26, 2026

Timeline

Disclosed

Dec 8, 2020

Last updated

Oct 20, 2026

Identifiers

CVE-2020-26234

GHSA-44cw-p2hm-gpf6

References

Advisorygithub.com · GHSA 44cw p2hm gpf6 Advisorynvd.nist.gov · CVE 2020 26234 Fixgithub.com · 4225bf90af74557deaf8fb6b80b0705c9621acfc

Related vulnerabilities

Also affects opencast-kernel

This CVE is medium severity; 6 of 6 other CVEs affecting opencast-kernel are rated as high or higher (top: critical).

CVE-2025-54380CVE-2017-1000221CVE-2021-32623CVE-2020-5231CVE-2020-5222CVE-2020-5206

Same weakness: CWE-346

This CVE is medium severity; 2 of 2 other CVEs with CWE-346 are rated as high or higher (top: critical).

CVE-2026-102895CVE-2026-63183Browse all CWE-346

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 20, 2026