CVE-2025-54530
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn JetBrains TeamCity before 2025.07 privilege escalation was possible due to incorrect directory permissions
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceIn JetBrains TeamCity versions prior to 2025.07, incorrect directory permissions on the server filesystem allowed unprivileged users or processes to modify or access sensitive directories, enabling privilege escalation to administrator or system-level privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2025.07CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify TeamCity versionCheck the installed TeamCity version by examining the version.txt file in the TeamCity installation directory, or log into the TeamCity web interface and navigate to the About page. Compare the version number to the affected range (prior to 2025.07).Affected if The installed version is less than 2025.07
-
Examine TeamCity home directory permissionsOn the TeamCity server filesystem, identify the TeamCity home directory (commonly /opt/TeamCity on Linux or C:\TeamCity on Windows). Use file system tools (ls -la on Linux or icacls on Windows) to list permissions on this directory and its subdirectories.Affected if Unprivileged users or processes have write or modify access to sensitive TeamCity directories such as the home directory, config, or logs subdirectories
-
Review configuration directory permissionsLocate the TeamCity configuration directory (typically <TeamCityHome>/conf or a dedicated data directory). Check file system permissions to determine if unauthorized accounts can read or modify configuration files.Affected if Non-service accounts have write access to configuration directories or can modify XML configuration files
-
Check log and temp directory permissionsExamine permissions on TeamCity log directories (typically <TeamCityHome>/logs) and temporary storage directories. Verify that these directories are not writable by unprivileged local users.Affected if Standard users have write permissions to log or temporary directories used by the TeamCity service
-
Inspect build agent directoriesIf build agents are configured, check the directory permissions on agent work and temp directories. These directories should not be writable by unprivileged users who could inject malicious code.Affected if Build agent directories permit write access from non-admin users
You are affected if TeamCity version is prior to 2025.07 AND unprivileged users have write or modify access to any TeamCity server directories that should be restricted to the service account only.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2025.07
Upgrade TeamCity to version 2025.07 or later. Alternatively, review and correct directory permissions on the TeamCity server to restrict write access to authorized service accounts only.
2025.07
- Upgrade JetBrains TeamCity to version 2025.07 or later to resolve the incorrect default permissions vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54530 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-54530 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data