dbcve.org
MavenApplication · Apache

CVE-2021-26291

CRITICAL · 9.1 CVSS v3.1 Published 2021-04-23
Fix available
A fix is available. Upgrade to 1.13.5 / 3.8.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Apache Maven will follow repositories that are defined in a dependency’s Project Object Model (pom) which may be surprising to some users, resulting in potential risk if a malicious actor takes over that repository or is able to insert themselves into a position to pretend to be that repository. Maven is changing the default behavior in 3.8.1+ to no longer follow http (non-SSL) repository references by default. More details available in the referenced urls. If you are currently using a repository manager to govern the repositories used by your builds, you are unaffected by the risks present in the legacy behavior, and are unaffected by this vulnerability and change to default behavior. See this link for more information about repository management: https://maven.apache.org/repository-management.html

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MavenApplication
Affected:< 3.8.1
QuarkusApplication
Affected:< 1.13.5
Financial Services Analytical Applications InfrastructureApplication
Affected:>= 8.0.6.0.0, <= 8.0.9.0.0>= 8.1.0.0.0, <= 8.1.2.0
Goldengate Big Data And Application AdaptersApplication
Affected:= 23.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.13.5 / 3.8.1 or later
Fixed in 1.13.53.8.1
Vendor patch www.oracle.com →
Recommended fix High confidence

Maven 3.8.1+ or Quarkus 1.13.5+

  1. Upgrade Apache Maven to version 3.8.1 or higher to obtain the default behavior change that blocks http (non-SSL) repository redirects
  2. If using Quarkus, upgrade to version 1.13.5 or higher which includes the Maven fix
  3. For Oracle Financial Services Analytical Applications Infrastructure (versions 8.0.6.0.0-8.0.9.0.0 and 8.1.0.0.0-8.1.2.0), apply the April 2022 Critical Patch Update from https://www.oracle.com/security-alerts/cpuapr2022.html
  4. For Oracle Goldengate Big Data And Application Adapters version 23.1, apply the April 2022 Critical Patch Update
  5. After upgrading, verify that builds function correctly with your internal repository manager using HTTPS
  6. If you have dependencies that explicitly require http repositories, either move them to HTTPS-enabled mirrors or explicitly configure them in your settings.xml with the <id> that needs to be allowed
Caveat Builds relying on http (non-SSL) external repositories will fail by default in 3.8.1+; these should be migrated to HTTPS or explicitly configured in settings.xml

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-26291 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-26291 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data