dbcve.org
ConjurApplication · Cyberark

CVE-2025-49827

CRITICAL · 9.8 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 →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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.22.0 and Secrets Manager, Self-Hosted (formerly known as Conjur Enterprise) 13.1 through 13.5 and 13.6 are vulnerable to bypass of the IAM authenticator. An attacker who can manipulate the headers signed by AWS can take advantage of a malformed regular expression to redirect the authentication validation request that Secrets Manager, Self-Hosted sends to AWS to a malicious server controlled by the attacker. This redirection could result in a bypass of the Secrets Manager, Self-Hosted IAM Authenticator, granting the attacker the permissions granted to the client whose request was manipulated. This issue affects both Secrets Manager, Self-Hosted (formerly Conjur Enterprise) and Conjur OSS. 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 · high confidence

Conjur's IAM authenticator contains a malformed regular expression that can be exploited through manipulation of AWS-signed headers. An attacker can redirect the authentication validation request that Conjur sends to AWS to a malicious server they control, bypassing the IAM authenticator and gaining the permissions of the legitimate client whose request was spoofed.

MitigationUpgrade immediately to Conjur OSS 1.22.1, Secrets Manager Self-Hosted 13.5.1, or 13.6.1 to obtain the patched regex. As a compensating control, restrict outbound network access from the Conjur server to only known AWS IAM endpoints.

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.19.5, < 1.22.1>= 13.1, < 13.5.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
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Check installed Conjur version
    Run 'conjur --version' or check the version via the Conjur API at /info endpoint, or inspect the Docker/container image tag if running containerized
    Affected if Version is >= 1.19.5 and < 1.22.1, or >= 13.1 and < 13.5.1
  2. Verify IAM authenticator is in use
    Examine Conjur configuration files (typically under /etc/conjur or /opt/conjur/etc) for 'iam-authenticator' or 'authn-iam' entries in authenticators.yml or policy files
    Affected if The IAM authenticator (authn-iam) is enabled and configured in Conjur's authentication methods
  3. Inspect IAM authenticator configuration
    Review the IAM authenticator configuration in /etc/conjur/authenticators.yml or related policy files, looking for the 'aws-iam' authentication method configuration
    Affected if The aws-iam authenticator is explicitly enabled in the authenticators configuration
  4. Check for unexpected AWS IAM endpoint configurations
    Review the IAM authenticator's configuration files and environment variables for any custom AWS IAM endpoint URLs that differ from official AWS IAM endpoints (verify against AWS documentation for expected endpoint patterns)
    Affected if A non-standard or unexpected AWS IAM endpoint URL is configured in the IAM authenticator settings

You are affected if your Conjur version falls within 1.19.5 to < 1.22.1 or 13.1 to < 13.5.1 AND the IAM authenticator (authn-iam) is enabled 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.22.1 / 13.5.1 or later
Fixed in 1.22.113.5.1
Interim mitigation

Upgrade immediately to Conjur OSS 1.22.1, Secrets Manager Self-Hosted 13.5.1, or 13.6.1 to obtain the patched regex. As a compensating control, restrict outbound network access from the Conjur server to only known AWS IAM endpoints.

Recommended fix High confidence

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

  1. 1. Identify the currently running Conjur version by checking the deployed containers or installed packages
  2. 2. If running Conjur OSS (versions 1.19.5 through 1.22.0), plan upgrade to version 1.22.1
  3. 3. If running Secrets Manager, Self-Hosted (versions 13.1 through 13.5 or 13.6), plan upgrade to version 13.5.1 or 13.6.1
  4. 4. Create a complete backup of the Conjur database, configuration files, and any custom policies before upgrading
  5. 5. Follow the standard Conjur upgrade documentation for your deployment type (OSS or Enterprise)
  6. 6. After upgrade, verify the IAM authenticator is functioning correctly by testing authenticated requests
  7. 7. Monitor logs to confirm no authentication anomalies

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

Fix this in Conjur Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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