CVE-2026-75048

This CVE-2026-75048 is a stored XSS in YouTrack's fenced code block language label—a metadata field that tells the syntax highlighter which rules to apply, not visible content itself. The 8.2 CVSS and 0.002 EPSS mismatch is the first thing to interrogate: the low exploitation probability likely reflects the multi-step attack chain (account compromise → markdown preview interaction → victim trigger) rather than a scoring failure. But that's not the real story. What's analytically important is the attack surface: the language identifier sits in a parsing layer that most sanitizers treat as inert configuration, not user content. The original markdown design assumed this field would be author-controlled, not attacker-controlled. When markdown renderers got embedded into collaboration platforms where every text field is untrusted input, that implicit trust assumption became a structural gap. YouTrack's role as a hub amplifies this significantly. Its automation chain—markdown preview in notifications, email digests, workflow triggers—means the trigger isn't just a user viewing a field; it's the entire downstream pipeline consuming rendered output. A compromised developer account could inject through this metadata path and reach any system connected to YouTrack's workflows. The deeper pattern: this isn't the first language-label injection. GitHub had it in 2014, GitLab subsequently. The remediation pattern exists—whitelist language identifiers, never treat metadata as inert, sanitize uniformly across parsing layers—but it's not being applied systematically. The class vulnerability isn't in markdown processors themselves; it's in how security-conscious applications wrap those processors without auditing the metadata path. For defenders: audit your markdown rendering stack for any field that configures display without being displayed. Review automation chains that consume rendered markdown. Check whether your integration layer applies content sanitization uniformly or only to visible output. The fix is simple once identified, but the class assumption (metadata is safe) is endemic to how this tooling gets built.

Reviewed through automated stages and approved by a human before publication.