Skip to main content
Exploitation reportedNot in CISA KEV yetFix available

CVE-2025-49831

Exploitation reported by one source. First attested on 2026-06-01 by GCVE · kevintel.

  • Published2025-07-15
  • Fixed in13.5.1 · 1.22.1
  • WeaknessCWE-287

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

An attacker of Secrets Manager, Self-Hosted installations that route traffic from Secrets Manager to AWS through a misconfigured network device can reroute authentication requests to a malicious server under the attacker’s control. CyberArk believes there to be very few installations where this issue can be actively exploited, though 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 may be affected. Conjur OSS version 1.22.1 and Secrets Manager, Self-Hosted versions 13.5.1 and 13.6.1 fix the issue.

Timeline

dates in UTC
  1. 2025-07-1521:15CVE publishedNVD
  2. 2026-06-0110:37Listed as exploited by GCVEGCVE
  3. 2026-06-0110:37Exploitation first reportedGCVE

Versions per branch

NVD
Cyberark conjur
BranchAffectedFixed in
13.5< 13.5.113.5.1
1.22< 1.22.11.22.1
13.6= 13.6no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • cyberark conjur
    Affected
    • = Conjur OSS < 1.22.1no fix stated
    • = Secrets Manager, Self-Hosted (formerly known as Conjur Enterprise) < 13.5.1no fix stated
    • = Secrets Manager, Self-Hosted (formerly known as Conjur Enterprise) = 13.6no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2025-07-15

Fix

  1. Update Cyberark conjur to 13.5.1 · 1.22.1

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • GCVEexploitation2026-06-01
  • CISA-ADPSSVC decisionnone2025-07-15
  • CNACVSS 4.09.1known since 2026-10-23
  • NVDCVSS 3.19.8read 2026-10-23
  • CNAweakness (CWE)CWE-287known since 2026-10-23
  • FIRST EPSSEPSS score1.2 %2026-11-18

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS 4.0 vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/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
Published
2025-07-15
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-2025-49831?

An attacker of Secrets Manager, Self-Hosted installations that route traffic from Secrets Manager to AWS through a misconfigured network device can reroute authentication requests to a malicious server under the attacker’s control. CyberArk believes there to be very few installations where this issue can be actively exploited, though 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 may be affected. Conjur OSS version 1.22.1 and Secrets Manager, Self-Hosted versions 13.5.1 and 13.6.1 fix the issue.

Is CVE-2025-49831 actively exploited?

Active exploitation of CVE-2025-49831 has not been confirmed. Its EPSS score was 1.2% on 2026-11-18, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2025-49831?

CVE-2025-49831 has a CVSS v3 base score of 9.8 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record