Cyber Resilience

CVE-2025-49828

Cyberark Conjur 1.20.1 – 1.21.2

Published
15 July 2025
Modified
17 June 2026
Patch / advisory
View advisory
CVSS Score v4 8.6
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.020 79th percentile
Risk Priority 34 floored blend · peak EPSS

Summary

CVE-2025-49828 is a high-severity Improper Neutralization of Special Elements Used in a Template Engine (CWE-1336) vulnerability in Cyberark Conjur. Its CVSS base score is 8.6 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Template Injection (T1221); ranked in the top 21% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-49828 is a remote code execution vulnerability (CWE-1336) affecting Conjur OSS versions 1.19.5 through 1.21.1 and Secrets Manager, Self-Hosted (formerly Conjur Enterprise) versions 13.1 through 13.4.1. Conjur provides secrets management and application identity for infrastructure. The flaw stems from an exposed API endpoint that allows an authenticated attacker who can inject secrets or templates into the Secrets Manager, Self-Hosted database to execute arbitrary Ruby code within the Secrets Manager process. The vulnerability has a CVSS v3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).

An authenticated attacker with the ability to inject secrets or templates into the database can exploit this remotely over the network with low complexity and no user interaction. Successful exploitation grants high-impact remote code execution within the Secrets Manager process, potentially leading to full compromise of the affected Conjur instance, including confidentiality, integrity, and availability violations.

Advisories recommend upgrading to Conjur OSS version 1.21.2 or Secrets Manager, Self-Hosted version 13.5, which fix the issue. Relevant resources include the CyberArk Conjur GitHub release notes at https://github.com/cyberark/conjur/releases/tag/v1.21.2 and security advisory at https://github.com/cyberark/conjur/security/advisories/GHSA-93hx-v9pv-qrm4, along with oss-security mailing list discussions.

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)
CWE-1336

Related Threats

MITRE ATT&CK Enterprise Techniques

T1221 Template Injection Stealth
Adversaries may create or modify references in user document templates to conceal malicious code or force authentication attempts.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-49830Same product: Cyberark Conjur
CVE-2025-49827Same product: Cyberark Conjur
CVE-2025-49829Same product: Cyberark Conjur
CVE-2025-49831Same product: Cyberark Conjur
CVE-2025-64087Shared CWE-1336
CVE-2026-44916Shared CWE-1336
CVE-2025-49136Shared CWE-1336
CVE-2025-32461Shared CWE-1336
CVE-2024-8238Shared CWE-1336
CVE-2025-57811Shared CWE-1336

Affected Assets

cyberark
conjur
1.20.1 — 1.21.2 · 13.1 — 13.5

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.3.2
  • V1.3.7
  • V1.3.10

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and static analysis can discover missing neutralization of template directives.

SI-10 Information Input Validation good match

Input validation rejects or sanitizes untrusted data before it reaches the template engine, stopping injection of special syntax.

SA-8 Security and Privacy Engineering Principles partial match

Security engineering principles require use of safe templating APIs and proper escaping of external input.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require proper input neutralization in template engines to prevent injection.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect template-injection flaws but does not itself implement neutralization controls.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates input validation and sanitization that directly prevents template-injection weaknesses.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for neutralizing special elements in template engines.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce the likelihood of unsafe template processing but do not prescribe specific neutralization techniques.

A.8.28 Secure coding partial match
prevents

Secure coding standards require proper escaping or sandboxing of template directives, directly mitigating CWE-1336.

References