Skip to main content
Mallory
MediumVulnerability

CVE-2026-113447: Session Fixation in VisualNet visualTicket

Published Nov 16, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days3 mentions · peak 3 in a dayToday
CVSS5.1Medium · v4
EPSS0.42%37th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-113447CWE-384 · Session Fixation

VisualNet visualTicket versions before 20260817 contain a session fixation vulnerability in session identifier handling. The application accepts a Symfony session identifier from the URL query string and sets it as a session cookie in the HTTP response, overwriting the browser's active session. An attacker can induce a victim to use an attacker-known session identifier and subsequently hijack the authenticated session.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an attacker to hijack a victim's authenticated session and impersonate the victim within the permissions granted to that session. The vulnerability also allows the victim's existing browser session to be overwritten with an attacker-selected session identifier.

Mitigation

If you can’t patch tonight, do this now.

As an interim measure, reject requests containing URL-supplied symfony session identifiers at a reverse proxy or application gateway, provided this control can be applied without disrupting required functionality. This is a compensating control, not a substitute for upgrading.

Remediation

Patch, then assume compromise.

Upgrade VisualNet visualTicket to version 20260817, which fixes this vulnerability.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-113447 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-113447 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-113447?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-113447.
Is there a patch for CVE-2026-113447?
Upgrade VisualNet visualTicket to version 20260817, which fixes this vulnerability.
How severe is CVE-2026-113447?
CVE-2026-113447 has a CVSS v4 score of 5.1 (Medium) and an EPSS score of 0.42% (37th percentile) as of Nov 17, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.