Subdomain Takeover in Interactsh server

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

EPSS

• CVE-2023-36474: 0.54% estimated exploitation activity in the next 30 days; percentile 45.41 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

A domain configured with interactsh server was vulnerable to subdomain takeover for specfic subdomain, i.e app, Interactsh server before < 1.0.0 used to create cname entries for app pointing to projectdiscovery.github.io as default which intended to used for hosting interactsh web client using GitHub pages. It turns out to be a security issue with a self-hosted interactsh server in which the user may not have configured a web client but still have a cname entry pointing to GitHub pages, making them vulnerable to subdomain takeover. This issue was initially reported to us as a subdomain takeover for one of our domains that runs interactsh server by Melih at security@projectdiscovery.io, and after conducting an internal investigation, we determined that it was an issue with the default config of interactsh server affecting all the server running self-hosted instance of interactsh, as a result - cname entry has been removed in the latest release. Impact This allows one to host / run…

Published by the source

27 Jan 2022, 15:15 UTC

Last modified by the source

10 Nov 2023, 05:05 UTC

Source last checked

26 Oct 2026, 15:00 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-m36x-mgfh-8g78

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-36474

Advisory: Subdomain Takeover in Interactsh server
IDs: CVE-2023-36474, GHSA-m36x-mgfh-8g78
Record: https://patchnext.com/advisories/cve-2023-36474 (revision 1, source checked 26 Oct 2026, 15:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/projectdiscovery/interactsh 1.0.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/projectdiscovery/interactsh: affected < 1.0.0; fixed in 1.0.0

## Suggested inspection (read-only)
- Go github.com/projectdiscovery/interactsh: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/projectdiscovery/interactsh.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-m36x-mgfh-8g78 (GitHub-reviewed advisory GHSA-m36x-mgfh-8g78 lists affected ranges: Go github.com/projectdiscovery/interactsh >=0 <1.0.0)

Commands are suggestions: review each one before running it.