dbcve.org
ConjurApplication · Cyberark

CVE-2025-49828

HIGH · 8.8 CVSS v3.1 Published 2025-07-15
Fix available
A fix is available. Upgrade to 1.21.2 / 13.5 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
Conjur provides secrets management and application identity for infrastructure. Conjur OSS versions 1.19.5 through 1.21.1 and Secrets Manager, Self-Hosted (formerly known as Conjur Enterprise) 13.1 through 13.4.1 are vulnerable to remote code execution An authenticated attacker who can inject secrets or templates into the Secrets Manager, Self-Hosted database could take advantage of an exposed API endpoint to execute arbitrary Ruby code within the Secrets Manager process. This issue affects both Secrets Manager, Self-Hosted (formerly Conjur Enterprise) and Conjur OSS. Conjur OSS version 1.21.2 and Secrets Manager, Self-Hosted version 13.5 fix the issue.

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 · high confidence

Conjur secrets management software contains an unsafe deserialization or template injection vulnerability in an API endpoint. An authenticated attacker with privileges to write secrets or templates to the database can inject malicious payloads that get evaluated as arbitrary Ruby code by the Secrets Manager process, leading to remote code execution.

MitigationUpgrade to Conjur OSS 1.21.2 or Secrets Manager Self-Hosted 13.5. In the interim, strictly limit database access and network exposure of the Secrets Manager API endpoints to reduce attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
ConjurApplication
Affected:>= 1.20.1, < 1.21.2>= 13.1, < 13.5

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Conjur version
    Run 'conjur --version' or check the Docker/container image tag, or inspect the package manager (apt/yum) for installed conjur package version
    Affected if Version is 1.20.1 through 1.21.1 (for Conjur OSS) or 13.1 through 13.4 (for Secrets Manager Self-Hosted)
  2. Verify API endpoint exposure
    Check network configuration files, load balancer settings, or firewall rules to determine if Conjur API endpoints (port 443/8080) are exposed to untrusted networks
    Affected if The Conjur API is accessible from networks beyond the trusted administrative zone
  3. Confirm authentication is enabled
    Inspect Conjur configuration files (conjur.yml or environment variables) for 'CONJUR_AUTHENTICATORS' setting and verify that authentication is not disabled
    Affected if Authentication is disabled or uses a weak/unauthenticated method, allowing unauthenticated access to the secrets/template API endpoints
  4. Review user privilege assignments
    Query Conjur database or use CLI 'conjur user list' and 'conjur policy load' to identify users/roles with 'execute' or 'write' privileges on the secrets or templates endpoints
    Affected if Users other than dedicated admins have write privileges to secrets or template resources in any loaded policy
  5. Check database access controls
    Review PostgreSQL database configuration (pg_hba.conf) and Conjur database connection settings to determine if the database is accessible from non-Conjur processes
    Affected if Database allows connections from compromised application servers or unauthorized hosts, enabling an attacker to inject malicious payloads

You are affected if your Conjur version falls within the vulnerable ranges AND the API endpoint is network-accessible AND an authenticated user with secrets/templates write privileges exists in your environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.21.2 / 13.5 or later
Fixed in 1.21.213.5
Interim mitigation

Upgrade to Conjur OSS 1.21.2 or Secrets Manager Self-Hosted 13.5. In the interim, strictly limit database access and network exposure of the Secrets Manager API endpoints to reduce attack surface.

Recommended fix High confidence

Conjur OSS 1.21.2 or Secrets Manager, Self-Hosted 13.5

  1. 1. Identify the Conjur product in use (Conjur OSS or Secrets Manager, Self-Hosted/Conjur Enterprise)
  2. 2. For Conjur OSS: upgrade to version 1.21.2 or later
  3. 3. For Secrets Manager, Self-Hosted (formerly Conjur Enterprise): upgrade to version 13.5 or later
  4. 4. Verify the upgrade by checking the Conjur version after installation
Caveat Review release notes for any breaking changes between current and target versions

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

Fix this in Conjur Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,560
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,296.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-49828 — 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-2025-49828 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