dbcve.org
ConjurApplication · Cyberark

CVE-2025-49829

MEDIUM · 6.5 CVSS v3.1 Published 2025-07-15
Fix available
A fix is available. Upgrade to 1.22.1 / 13.5.1 or later.
See remediation →
71/100
Remediation priority · Elevated
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. Missing validations in Secrets Manager, Self-Hosted allows authenticated attackers to inject resources into the database and to bypass permission checks. This issue affects Secrets Manager, Self-Hosted (formerly Conjur Enterprise) prior to versions 13.5.1 and 13.6.1 and Conjur OSS prior to version 1.22.1. Conjur OSS version 1.22.1 and Secrets Manager, Self-Hosted versions 13.5.1 and 13.6.1 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 · moderate confidence

This is a missing input validation vulnerability in Conjur Secrets Manager that allows authenticated attackers to inject arbitrary resources into the database and bypass built-in permission checks. The flaw affects both Conjur OSS (prior to 1.22.1) and Secrets Manager Self-Hosted (prior to 13.5.1/13.6.1), enabling authenticated users to perform unauthorized operations beyond their intended access scope.

MitigationUpgrade to Conjur OSS 1.22.1 or Secrets Manager Self-Hosted 13.5.1/13.6.1 to obtain the patched versions with proper validation and permission enforcement.

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.22.1< 13.5.1= 13.6

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
None
Integrity
High
Availability
None

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

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 changelog file typically found in /opt/conjur/CHANGELOG or the packaged version file
    Affected if The version displayed is below 1.22.1 for Conjur OSS, below 13.5.1 for Self-Hosted, or exactly 13.6.0
  2. Determine Conjur product variant
    Check whether the installation is Conjur OSS (open source) or CyberArk Secrets Manager Self-Hosted by inspecting the product name in the UI, startup logs, or package metadata
    Affected if The product is either Conjur OSS or Secrets Manager Self-Hosted and the version falls into the affected ranges from step 1
  3. Verify authentication is enabled
    Confirm that user authentication is configured and active - check /etc/conjur.yml or the conjur.yml configuration file for authn settings, and verify users exist in the system
    Affected if Authentication is enabled and users can log in (the vulnerability affects authenticated users, so if no users exist the attack surface is reduced but the flaw still exists in the code)
  4. Confirm database is in use
    Verify the Conjur deployment uses a persistent database (PostgreSQL) by checking the DATABASE_URL environment variable or configuration in conjur.yml
    Affected if A database backend is configured and active (the vulnerability allows injection of arbitrary resources into this database)

You are affected if your Conjur installation version is below 1.22.1 for OSS, below 13.5.1 for Self-Hosted, or exactly 13.6, and you have authenticated users configured in the 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.22.1 / 13.5.1 or later
Fixed in 1.22.113.5.1
Interim mitigation

Upgrade to Conjur OSS 1.22.1 or Secrets Manager Self-Hosted 13.5.1/13.6.1 to obtain the patched versions with proper validation and permission enforcement.

Recommended fix High confidence

Conjur OSS: 1.22.1; Secrets Manager, Self-Hosted: 13.5.1 or 13.6.1

  1. 1. Identify the currently running Conjur product and version (Conjur OSS or Secrets Manager, Self-Hosted)
  2. 2. For Conjur OSS: If version is less than 1.22.1, upgrade to version 1.22.1
  3. 3. For Secrets Manager, Self-Hosted: If version is less than 13.5.1 or exactly 13.6, upgrade to version 13.5.1 or 13.6.1
  4. 4. After upgrade, verify that the missing authorization vulnerability is resolved by confirming the versions are running correctly
  5. 5. Test that resource injection and permission bypass vulnerabilities are no longer exploitable

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

Fix this in Conjur Scoped from the published advisory
  • Consultation5.0 h
  • Implementation10.0 h
  • Testing8.0 h
  • Review / QA4.0 h
27.0 hours of engineering $4,720
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,552.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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