VulnerabilityPublished 29 May 2026

CVE-2026-49377: JetBrains TeamCity · CWE-526

Affects JetBrains TeamCitySource CVE Database V5

Compare

Not known to be exploited · CVSS 4.3 Medium : upgrade to 2025.11.2 when convenient.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2025.11.2

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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 29 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity 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

Upgrade TeamCity and org.jetbrains.teamcity/teamcity-server to 2025.11.2.

Affected software

Product	Affected	Fixed in
JetBrainsTeamCity	Affected <2025.11.2	Fixed in 2025.11.2
Mavenorg.jetbrains.teamcity/teamcity-server`pkg:maven/org.jetbrains.teamcity/teamcity-server`Other threats	Affected <2025.11.2	Fixed in 2025.11.2

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

AI-suggested

If you cannot patch yet, consider restricting access to TeamCity agents and sensitive configuration data to trusted personnel only.

Description

CVE-2026-49377 is a medium severity vulnerability in JetBrains TeamCity before version 2025.11.2. It involves the exposure of sensitive data through default agent parameters. The vulnerability is identified as CWE-526, which relates to exposure of sensitive information. The CVSS score is 4.3, indicating a medium impact primarily due to confidentiality loss without impact on integrity or availability.

Impact

The impact is limited to confidentiality loss of sensitive data through default agent parameters. There is no reported impact on integrity or availability. No known exploits have been observed in the wild, reducing immediate risk. However, sensitive information exposure could potentially aid attackers in further reconnaissance or targeted attacks if leveraged.

Summary

This vulnerability in JetBrains TeamCity allows sensitive data to be exposed via default agent parameters in versions prior to 2025.11.2. It is classified under CWE-526, which concerns exposure of sensitive information. The CVSS 3.1 base score is 4.3, reflecting a network attack vector with low complexity, requiring low privileges and no user interaction, resulting in limited confidentiality impact.

CWE-526Cleartext Storage of Sensitive Information in an Environment Variable (opens in a new tab)
Variant weaknessOWASP Top 10 A02:2025: Security Misconfiguration (opens in a new tab)
The product uses an environment variable to store unencrypted sensitive information.
Architecture and Design
Encrypt information stored in the environment variable to protect it from being exposed to an unauthorized user. If encryption is not feasible or is considered too expensive for the business use of the application, then consider using a properly protected configuration file instead of an environment variable.
Implementation
If the environment variable is not necessary for the desired behavior, then remove it entirely, or clear it to an empty value.
OWASP ASVS 4.0.3
V8.1.6 (opens in a new tab)
V8.2.3 (opens in a new tab)
V8.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

jetbrains.com/privacy-security/issues-fixed/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Jun 2026, 21:21 UTC

WeaknessesCWE-526

Technical details

References

Community reviews

Related threats