Skip to main content
CVE-2025-49829VulnerabilityPublished Updated

CVE-2025-49829: cyberark conjur · Missing Authorization

Affects cyberark conjurSource CVE Database V5

0

Not known to be exploited · CVSS 6.0 Medium : upgrade to 1.22.1 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
6.0Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.22.1
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Jul 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade cyberark/conjur to 1.22.1.

Affected software

ProductAffectedFixed in
GitHubcyberark/conjurpkg:github/cyberark/conjurOther threatsAffected
  • <1.22.1
Fixed in
  • 1.22.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Upgrade affected CyberArk Conjur products to the fixed versions: Conjur OSS 1.22.1 or later, and Secrets Manager, Self-Hosted versions 13.5.1 or 13.6.1 or later. 2. Implement strict access controls to limit authenticated user privileges to the minimum necessary, reducing the risk of low-privilege users exploiting the vulnerability. 3. Monitor logs and audit trails for unusual resource injection activities or permission bypass attempts within the secrets management system. 4. Employ network segmentation and zero-trust principles to restrict access to the secrets manager to only trusted and verified systems and users. 5. Conduct regular security reviews and penetration testing focused on authorization mechanisms in secrets management solutions. 6. Educate administrators and DevOps teams on the importance of timely patching and monitoring of secrets management platforms. 7. Consider deploying runtime detection tools that can identify anomalous behavior indicative of unauthorized resource injection or privilege escalation attempts.

Description

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.

References

Community reviews

Loading reviews…