Sonatype Nexus Repository Pro Self-Hosted

Commercial self-hosted artifact repository with supported high-availability deployment across customer cloud infrastructure.

11 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

Nexus Repository 3.98.0 security update

Seven November advisories cover privilege escalation, SSO account reactivation, exposed signing credentials, SQL injection, stored XSS, and repository-member authorization bypass.

Scope: Affected ranges vary from 3.0.0 through 3.97.x to narrower 3.86–3.97, 3.90–3.97, 3.93–3.97, and 3.94–3.97 ranges. All are fixed in 3.98.0.

Rut Auth, SSO, YUM or repository signing, the optional reindex task, OCI attestations, and repository groups determine applicability.

Action: Upgrade to 3.98.0 or later. The upgrade retains existing Rut Auth capabilities and repository-group memberships: remove unused Rut Auth capabilities and realms, confirm intended capabilities were administrator-created, and remove group members that group editors are not allowed to read. Review disabled or locked SSO users' sign-ins and affected reindex tasks; rotate potentially exposed signing keys and passphrases.

Primary source · CVE-2026-113374 · CVE-2026-113372 · CVE-2026-113371 · CVE-2026-113370 · CVE-2026-113369 · CVE-2026-113368 · Reviewed 2026-11-18

Nexus Repository Java4Shell fixes for current and maintained branches

Nexus Repository 3.98.2 includes Java4Shell mitigation; 3.90.7 and 3.88.2 are separate older-line backports, not substitutes for the current 3.98-line fix.

Scope: Self-hosted Nexus Repository: 3.98.2 on the 3.98 line. The FAQ also lists 3.97.4, 3.95.6, 3.94.4, 3.93.4 and 3.92.5; the linked November 19 notes identify 3.90.7 and 3.88.2.

Installed branch, bundled JDK, CPU and process restart determine applicability.

Action: Upgrade the installed supported branch to its fixed release, including 3.98.2 or later on 3.98. Restart and verify affected processes. If an immediate upgrade is unavailable, follow Sonatype’s temporary JVM mitigation and runtime-compatibility guidance. Do not downgrade to match an older maintenance backport.

Primary source · 3.90.7 release notes · 3.88.2 release notes · 3.98.2 current-line fix, released November 18, 2026 · Reviewed 2026-11-19

What lands where

  1. Supplied by

    Vendor or project

    Official Helm chart for resilient or high-availability Kubernetes deployments, or supported standalone and Docker installation paths

  2. Operated by

    Your team

    Customer manages compute or Kubernetes, PostgreSQL, blob and node storage, ingress and load balancing, TLS, secrets, backups, monitoring, upgrades and license persistence.

Deployment boundaries by provider

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodOfficial Helm chart for resilient or high-availability Kubernetes deployments, or supported standalone and Docker installation paths
InfrastructureServers / containers
Nexus Repository Pro runs on persistent VM or Kubernetes capacity with durable node storage, blob storage and, for resilient or HA deployments, an external PostgreSQL database.
Licensing modelCommercial Only
A Sonatype license file unlocks Nexus Repository Pro capabilities; unlicensed self-hosted instances operate as Community Edition, while the selected high-availability deployment requires Pro.
LicenseCommercial Nexus Repository Pro license required for high availability and other Pro capabilities.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

9 of 12 fields researched (75%) · 8 documented · 1 unresolved. Evidence coverage is not a feature score.

Marketplace delivery
Edition-dependentEvidence and scope for Marketplace delivery

Sonatype publishes an AWS Marketplace offer explicitly named Nexus Repository Pro (Self-Hosted). It is a contract/license procurement listing classified as SaaS, not a vendor-run Repository Cloud deployment or an infrastructure installer. Confirm usage, renewal and support terms.

Vendor-published AWS offer; procurement and application hosting are distinct · Source ↗ · Offer prodview-444trrzad4z56 ↗ — Sonatype; Self-hosted license contract; AWS delivery classification SaaS · Reviewed 2026-11-16

Edition-dependent · Editor reviewed.

Single sign-on
Edition-dependentEvidence and scope for Single sign-on

Licensed self-hosted Nexus Repository supports SAML 2.0 browser SSO, including IdP group attributes for authorization. SAML authenticates the UI; repository clients use other supported credentials such as user tokens.

Nexus Repository Pro self-hosted UI; not Community or a repository-content SAML protocol · Source ↗ · Reviewed 2026-11-16

Edition-dependent · Editor reviewed.

SCIM provisioning
Not availableEvidence and scope for SCIM provisioning

Sonatype explicitly states that direct SCIM is unsupported. SSO does not automatically synchronize user lifecycle or group changes; manual management or custom API integrations are required.

Nexus Repository direct SCIM integration · Source ↗ · Separate SAML-user management REST API ↗ · Reviewed 2026-11-16

Explicitly unsupported · Editor reviewed.

Security controls
DocumentedEvidence and scope for Security controls

The policy requires base usage telemetry and administrator acknowledgment starting in 3.97.0. Pro has a stated 45-day telemetry-delivery grace period; customers requiring disconnected operation need entitlement-specific support review. This is an egress requirement, not a security attestation. Current advisory review: Seven November advisories cover privilege escalation, SSO account reactivation, exposed signing credentials, SQL injection, stored XSS, and repository-member authorization bypass. Upgrade to 3.98.0 or later. The upgrade retains existing Rut Auth capabilities and repository-group memberships: remove unused Rut Auth capabilities and realms, confirm intended capabilities were administrator-created, and remove group members that group editors are not allowed to read. Review disabled or locked SSO users' sign-ins and affected reindex tasks; rotate potentially exposed signing keys and passphrases. Current review: Nexus Repository 3.98.2, released November 18, 2026, includes Java4Shell mitigation for CVE-2026-114938 on the 3.98 line. Sonatype also identifies fixes for other maintained branches, including 3.97.4, 3.95.6, 3.94.4, 3.93.4 and 3.92.5; the November 19 notes separately document 3.90.7 and 3.88.2 backports. Use the fixed release for the installed supported branch, restart affected processes and verify the active Java runtime or mitigation; do not downgrade to an older branch to match a backport.

Nexus Repository maintenance lines explicitly covered by the November 19 release notes · Source ↗ · Prior security-controls source ↗ · Prior security-controls source ↗ · CVE-2026-113374 ↗ · CVE-2026-113372 ↗ · CVE-2026-113371 ↗ · CVE-2026-113370 ↗ · CVE-2026-113369 ↗ · CVE-2026-113368 ↗ · 3.90.7 release notes ↗ · 3.88.2 release notes ↗ · 3.98.2 current-line Java4Shell mitigation ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Air-gapped operation
Not confirmedEvidence and scope for Air-gapped operation

The current telemetry policy requires base usage reporting and directs commercially entitled customers needing disconnected operation to Sonatype Support. It does not publish an unconditional Pro exemption or a complete disconnected procedure; obtain entitlement-specific terms before relying on air-gapped operation.

Current self-hosted Pro telemetry policy, including 3.97+ onboarding; not Community or SAGE · Source ↗ · Reviewed 2026-11-16

Sources checked — unresolved · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

Sonatype publishes the nxrm-ha Helm chart for resilient and high-availability deployments. Pro HA requires an external PostgreSQL database and persistent storage; choose a supported chart, application and database combination.

Nexus Repository Pro HA; not the standalone Community Edition topology · Source ↗ · Deployment artifact ↗ (main (moving branch)) · HA requirements ↗ · Reviewed 2026-11-16

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

The current cloud-native XS profile recommends one node with 4 vCPU and 16 GiB RAM for its stated 100 requests/second workload. Larger profiles increase node count and resources; Pro HA additionally needs a load balancer, shared blob storage and external PostgreSQL.

Per-node example for the documented workload; not an HA total or performance guarantee · Source ↗ · HA infrastructure requirements ↗ · Reviewed 2026-11-16

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

A Sonatype license file unlocks Nexus Repository Pro capabilities; unlicensed self-hosted instances operate as Community Edition, while the selected high-availability deployment requires Pro.

Sonatype Nexus Repository Pro Self-Hosted: software license terms; infrastructure and operating costs are separate · Source ↗ · Edition and license conditions ↗ · Reviewed 2026-11-16

Documented · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

Nexus Repository 3.98.2 was released November 18, 2026 and includes Java4Shell mitigation for CVE-2026-114938. This is the reviewed 3.98-line snapshot; 3.90.7 and 3.88.2 are separate maintenance backports. Check commercial-edition, runtime, Helm and HA compatibility before upgrading.

Self-hosted Nexus Repository release; commercial edition and HA compatibility still govern use; source supplies a publication day, not a timestamp · Source ↗ · 3.90.7 maintenance-line mitigation ↗ · 3.88.2 maintenance-line mitigation ↗ · Sonatype Java4Shell product and maintained-branch guidance ↗ · Reviewed 2026-11-19

Documented · Editor reviewed.

Show all fields (3 not researched)
Cloud commitment eligibility
Not researched Supply a public source.
Compliance attestations
Not researched Supply a public source.
Operating cost estimate
Not researched Supply a public source.

Scope & considerations

This entry covers Nexus Repository Pro self-hosted deployments, not Nexus Repository Cloud or the unlicensed Community Edition. High availability requires Pro, an external PostgreSQL database and customer expertise in Kubernetes, Helm and cloud infrastructure. Sonatype states that its support expertise is strongest on AWS even though Azure and Google Cloud infrastructure are supported. Container deployments must persist both nexus-data and Java preferences so license state survives restarts. Nexus Repository 3.98.0 fixes seven November advisories covering Rut Auth privilege escalation, disabled or locked SSO users regaining access, exposed signing material, SQL injection in the optional reindex task, stored XSS, and group-member authorization bypass. After upgrading, remove unused Rut Auth capabilities and realms, confirm intended capabilities were administrator-created, and remove existing group members that group editors are not allowed to read; the upgrade does not clean these up. Review affected sign-ins and tasks, and rotate potentially exposed signing keys or passphrases. Nexus Repository 3.98.2, released November 18, 2026, includes Java4Shell mitigation for CVE-2026-114938 on the 3.98 line. Sonatype also identifies fixes for other maintained branches, including 3.97.4, 3.95.6, 3.94.4, 3.93.4 and 3.92.5; the November 19 notes separately document 3.90.7 and 3.88.2 backports. Use the fixed release for the installed supported branch, restart affected processes and verify the active Java runtime or mitigation; do not downgrade to an older branch to match a backport.

Category fit

DevOps
Provides a self-managed repository for packages, containers and other build artifacts used by software-delivery pipelines.

Compare within DevOps

  • Argo CDGitOps continuous delivery controller and interface for deploying and reconciling applications in Kubernetes clusters.
    • AWS
    Customer-operated · Open Source / Open Core
  • Azure DevOps ServerSource control, CI/CD, work tracking, testing and package management installed on Azure virtual machines you operate.
    • Azure
    Customer-operated · Commercial Only
  • Bitbucket Data CenterCommercial self-managed Git collaboration and code-review platform for eligible existing Atlassian customers, with an announced Hybrid License transition.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • CircleCI ServerCommercial self-hosted CI/CD platform installed in a customer-operated Amazon EKS or Google GKE cluster.
    • AWS
    • Google Cloud
    Customer-operated · Commercial Only
  • CloudBees CI on Modern Cloud PlatformsEnterprise continuous-integration platform installed with Helm in a Kubernetes cluster you operate.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • GitHub Enterprise ServerCustomer-operated GitHub software-development platform deployed as a licensed virtual appliance.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • GitLab Self-ManagedSource control and CI/CD on infrastructure you operate.
    • AWS
    • Azure
    • Google Cloud
    • Oracle Cloud
    • Alibaba Cloud
    Customer-operated · Open Source / Open Core
  • HarborContainer and OCI artifact registry for managing software images within customer-operated infrastructure.
    • Railway
    Customer-operated · Open Source / Open Core

Showing 8 of 27 other listings in DevOps. These products address related workflows; read their category-fit notes before comparing scope. See all of DevOps →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • Supported Nexus Repository Pro high-availability infrastructure ↗ · AWS, Azure, Google Cloud

      Vendor / upstream documentation · Reviewed 2026-11-16 · Scope: Nexus Repository Pro. Vendor support commitment: not assessed; confirm the selected release and contract.

      Sonatype explicitly lists AWS, Azure and Google Cloud as supported providers for Nexus Repository Pro HA and names EKS, AKS and GKE together with provider-specific databases, storage and blob services.

    • Nexus Repository Pro deployment on Google Cloud ↗ · Google Cloud

      Vendor / upstream documentation · Reviewed 2026-11-16 · Scope: Nexus Repository Pro. Vendor support commitment: not assessed; confirm the selected release and contract.

      Sonatype provides a concrete Google Cloud deployment path for Nexus Repository Pro using its resiliency and high-availability Helm chart, GKE ingress, persistent storage and license management.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory