Skip to main content
Mallory
MediumVulnerability

CVE-2026-113445: Information Disclosure in VisualNet visualTicket Order Creation

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
CVSS6.9Medium · v4
EPSS0.50%44th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-113445CWE-209 · Generation of Error Message…

VisualNet visualTicket versions before 20260817 expose sensitive database information through error messages in the order creation functionality. An otherwise valid checkout request containing an invalid payment_type value triggers a detailed SQL/ORM exception that is returned to the client rather than retained exclusively in server-side logs. A remote unauthenticated attacker can disclose the database name, table and column names, query structure, and foreign key constraint name.

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.

Unauthenticated remote attackers can obtain internal database names, schema details, query structure, and foreign key constraint information. These disclosures reveal implementation details that may facilitate further targeted attacks; this vulnerability does not itself establish database modification or code execution.

Mitigation

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

Return generic client-facing error messages and retain detailed SQL/ORM exceptions exclusively in access-controlled server-side logs.

Remediation

Patch, then assume compromise.

Upgrade VisualNet visualTicket to version 20260817 or a later version containing the fix.

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-113445 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-113445 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-113445?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-113445.
Is there a patch for CVE-2026-113445?
Upgrade VisualNet visualTicket to version 20260817 or a later version containing the fix.
How severe is CVE-2026-113445?
CVE-2026-113445 has a CVSS v4 score of 6.9 (Medium) and an EPSS score of 0.50% (44th percentile) as of Nov 17, 2026.
Activity feed

Recent activity

3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
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.