Skip to content
KitploitKITPLOIT
ToolsBlog
Submit
ToolsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

··Feeds·Contact·Privacy·© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE-2026-63077 — CVE-2026-63077 — Unauthenticated Remote Code Execution in JetBrains TeamCity via agent polling protocol deserialization. CVSS 9.8 CRITICAL. Mass exploitation tool with interactive shell, multi-threading, and real-time result logging. | Kitploit
Tools/GitHubGitHub/anggatechi/cve-2026-63077
ExploitationWeb Application ExploitationWeb SecurityPenetration TestingPayload Development
GitHubanggatechi/cve-2026-63077

CVE-2026-63077

CVE-2026-63077 — Unauthenticated Remote Code Execution in JetBrains TeamCity via agent polling protocol deserialization. CVSS 9.8 CRITICAL. Mass exploitation tool with interactive shell, multi-threading, and real-time result logging.

View Repository
251 month agoNot yet reviewed

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share

Animated project summary

CVE-2026-63077 CVSS 3.1 score 9.8 CWE-502 TeamCity On-Premises Python 3.9 or later

Overview • Visual Flow • Requirements • Usage • Limitations • Mitigation

[!CAUTION] This PoC executes an operating-system command and can modify the TeamCity application directory. Use it only in an isolated lab or against systems for which you have explicit written authorization.

⚡ Overview

PropertyValue
CVECVE-2026-63077
ProductJetBrains TeamCity On-Premises
ImpactUnauthenticated remote code execution through the agent polling protocol
WeaknessCWE-502 — Deserialization of Untrusted Data
CVSS9.8 Critical — JetBrains CNA, CVSS 3.1
AuthenticationNot required
Fixed releases2025.11.7 and 2026.1.3
Alternative mitigationJetBrains security patch plugin for TeamCity 2017.1+
TeamCity CloudNo customer action required according to JetBrains

JetBrains states that all TeamCity On-Premises releases before the fixed versions are affected. Upgrade to a current supported release whenever possible. If an immediate upgrade is not possible, follow the vendor's instructions for its security patch plugin.

[!NOTE] This repository does not claim that the CVE is listed in the CISA Known Exploited Vulnerabilities catalog. JetBrains reported no known active exploitation when it published its advisory on July 27, 2026.

🧬 Visual flow

Animated high-level proof-of-concept flow

At a high level, the PoC:

  1. registers a temporary TeamCity agent session;
  2. submits a serialized XML object graph to the agent command endpoint;
  3. attempts to write a one-shot JSP file under the TeamCity web root;
  4. requests that file to execute the supplied command; and
  5. records successful command output in result.txt.

The generated JSP attempts to delete itself when invoked. Treat cleanup as best-effort, not as a guarantee that the target is left unchanged.

🧰 Requirements

root@kitploit:~
Python       3.9 or later
Target       Authorized TeamCity On-Premises lab instance
Transport    HTTP or HTTPS access
Shell        bash available on the TeamCity server
Packages     Python standard library only
Safety       Disposable environment or verified backup

[!IMPORTANT] The payload invokes commands through bash -c. A Windows TeamCity server therefore requires a compatible Bash installation; otherwise the command execution stage will fail.

🚀 Authorized lab usage

Run the PoC from the project directory:

root@kitploit:~
python3 exploit.py

The program asks for a target, a command, and the desired thread count:

root@kitploit:~
[*] Target URL or file: http://127.0.0.1:8111
[*] Command: id
[*] Threads (default 10): 1

Single lab target

Enter the target's full base URL. When the scheme is omitted, the script uses http:// automatically.

Authorized target file

For multiple lab systems, enter the path to a text file with one URL per line:

root@kitploit:~
http://127.0.0.1:8111
http://192.0.2.10:8111
https://teamcity.lab.example

Do not add inline comments to target lines because the parser does not remove them. Start with one thread and increase concurrency only after confirming the scope and capacity of the authorized lab.

📄 Output

Successful results are appended to result.txt:

root@kitploit:~
http://127.0.0.1:8111 -> uid=1000(tcuser) gid=1000(tcuser) groups=1000(tcuser)

The file may contain sensitive command output. Keep it out of version control and delete it securely when it is no longer required.

⚠️ Known limitations

  • TLS certificate verification is disabled by the current HTTP helper. Use the PoC only on a trusted test network.
  • Command execution assumes that bash is available on the TeamCity server.
  • The web-root path is hard-coded to ../webapps/ROOT; nonstandard TeamCity or servlet-container layouts may not work.
  • A failed attempt does not prove that a target is patched. Network controls, reverse proxies, file permissions, layout differences, and endpoint changes can produce the same result.
  • The single-target follow-up prompt currently references an undefined args object. The first submitted command runs independently, but additional commands from that prompt will fail until the code is corrected.

🛡️ Defensive guidance

root@kitploit:~
flowchart LR
    A["Identify TeamCity version"] --> B{"Patched release?"}
    B -- "No" --> C["Upgrade to 2025.11.7 / 2026.1.3+"]
    B -- "Upgrade blocked" --> D["Apply JetBrains security patch plugin"]
    C --> E["Restrict access to trusted networks or VPN"]
    D --> E
    E --> F["Review logs, credentials, artifacts, and pipelines"]
  1. Upgrade TeamCity On-Premises to 2025.11.7, 2026.1.3, or a newer supported release.
  2. If upgrading immediately is impossible, install JetBrains' security patch plugin for supported older releases.
  3. Restrict TeamCity access to trusted networks or a VPN. Avoid exposing the login page and APIs directly to the internet.
  4. Run the TeamCity server process with the minimum operating-system privileges it requires.
  5. Keep the TeamCity server on a dedicated host separate from build agents.
  6. After suspected exploitation, preserve evidence and investigate the server, stored credentials, build artifacts, and downstream CI/CD systems.

⚖️ Responsible-use notice

This code is provided for security research, validation, and defensive testing in environments you own or are explicitly authorized to assess. You are responsible for complying with applicable laws, contracts, and rules of engagement. The author and contributors accept no liability for unauthorized use or resulting damage.

📚 References

  • JetBrains security advisory
  • JetBrains fixed security issues
  • NVD entry for CVE-2026-63077
  • TeamCity upgrade documentation

Download Tool