VulnerabilityPublished 10 Dec 2025

CVE-2025-62181: Pegasystems Pega Infinity · Observable Response Discrepancy

Affects Pegasystems Pega InfinitySource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 09:08 UTC

CVSS 3.1 base score

5.3Medium

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.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Pegasystems Pega Infinity	Affected =7.1.0	Fixed in–

AI-suggested

European organizations should take the following specific actions to mitigate this vulnerability: 1) Immediately identify and inventory all Pega Infinity instances and verify if the deprecated basic-authentication feature is enabled. 2) Upgrade affected Pega Infinity installations to the patched versions 24.1.4, 24.2.4, or 25.1.1 as soon as possible to apply the official fix. 3) Disable the basic-authentication feature entirely and migrate to more secure authentication mechanisms such as OAuth 2.0, SAML, or OpenID Connect, which do not exhibit this vulnerability. 4) Implement monitoring and alerting for unusual authentication patterns that may indicate enumeration attempts, such as repeated failed logins with varying usernames. 5) Conduct user awareness training to reduce the risk of social engineering attacks that could leverage enumerated usernames. 6) Review and enforce strong password policies and consider multi-factor authentication to reduce the risk of account compromise following enumeration. 7) Regularly audit and update authentication configurations in Pega Infinity to align with security best practices and vendor recommendations. These steps go beyond generic advice by focusing on the deprecated feature removal, patch application, and enhanced detection capabilities.

Description

Pega Platform versions 7.1.0 through Infinity 25.1.0 are affected by a User Enumeration. This issue occurs during user authentication process, where a difference in response time could allow a remote unauthenticated user to determine if a username is valid or not. This only applies to deprecated basic-authentication feature and other more secure authentication mechanisms are recommended. A fix is being provided in the 24.1.4, 24.2.4, and 25.1.1 patch releases. Please note: Basic credentials authentication service type is deprecated started in 24.2 version: https://docs.pega.com/bundle/platform/page/platform/release-notes/security/whats-new-security-242.html.

Impact

For European organizations, this vulnerability primarily poses a risk of user enumeration, which can aid attackers in gathering valid usernames from Pega Infinity deployments. This reconnaissance can facilitate subsequent attacks such as credential stuffing, brute force, or social engineering campaigns targeting identified users. While the vulnerability does not directly compromise data confidentiality, integrity, or availability, the exposure of valid usernames can increase the attack surface and risk of account compromise. Organizations in sectors with high-value targets such as finance, government, healthcare, and large enterprises using Pega Infinity with basic authentication enabled are particularly at risk. The impact is heightened in environments where username disclosure can lead to further exploitation or where user credentials are reused across systems. Given that the basic-authentication feature is deprecated, continued use of this mechanism increases exposure. The vulnerability's medium severity suggests it should be addressed promptly but does not represent an immediate critical threat. However, failure to remediate could facilitate more damaging attacks leveraging the enumerated usernames.

Summary

CVE-2025-62181 is a user enumeration vulnerability classified under CWE-204 affecting Pegasystems Pega Infinity versions 7.1.0 through 25.1.0. The issue arises during the user authentication process when the deprecated basic-authentication feature is used. Specifically, an attacker can remotely send authentication requests with different usernames and observe subtle differences in response times or error messages. These observable discrepancies allow the attacker to infer whether a username exists in the system without needing valid credentials or user interaction. This type of vulnerability facilitates reconnaissance activities that can precede more targeted attacks such as credential stuffing or phishing. The vulnerability does not directly expose passwords or sensitive data, nor does it allow modification or denial of service. The basic-authentication feature, which is less secure, has been deprecated starting with Pega Infinity version 24.2, and organizations are encouraged to migrate to more secure authentication mechanisms like OAuth or SAML. Patches addressing this vulnerability have been released in versions 24.1.4, 24.2.4, and 25.1.1. No known exploits are currently reported in the wild. The CVSS v3.1 base score is 5.3, indicating a medium severity level, with network attack vector, low attack complexity, no privileges or user interaction required, and limited confidentiality impact.

CWE-204Observable Response Discrepancy (opens in a new tab)
Base weakness
The product provides different responses to incoming requests in a way that reveals internal state information to an unauthorized actor outside of the intended control sphere.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
Implementation
Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended).
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
ICMP IP Total Length Field Probe (opens in a new tab)
ICMP IP 'ID' Field Error Message Probe (opens in a new tab)
Application Fingerprinting (opens in a new tab)
System Footprinting (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

support.pega.com/support-doc/pega-security-advisory-j25-vulnerability-remediation-note (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Dec 2025, 23:14 UTC

WeaknessesCWE-204

Technical details

References

Community reviews

Related threats