Authenticated build parameter disclosure via improper permission checks
Published May 29, 2026 · Updated May 29, 2026
Missing authorization in JetBrains TeamCity before 2026.1 allows remote authenticated users to expose build configuration parameters. JetBrains identifies improper permission checks in build-configuration parameter handling but has not published the affected endpoint or exact failed check. A low-privilege account and network access are required; parameter disclosure is the only consequence described in the public technical record.
Summary
What happened
Missing authorization in JetBrains TeamCity before 2026.1 allows remote authenticated users to expose build configuration parameters. JetBrains identifies improper permission checks in build-configuration parameter handling but has not published the affected endpoint or exact failed check. A low-privilege account and network access are required; parameter disclosure is the only consequence described in the public technical record.
The record
- CVE
- CVE-2026-49374
- Published
- May 29, 2026
- Updated
- May 29, 2026
- Vendor
- JetBrains
- Product
- TeamCity On-Premises
- Classifications
- CWE-862
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 29, 2026CVE publishedPublication date reported by the CVE source.
- May 29, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2026.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo