CVE
Integra32 Security Management System remote code execution in .NET Remoting service
Affects Integra32 Security Management System 5.1.11 R5.0 or earlier where the deprecated .NET Remoting service is exposed on TCP port 2001. The checked facts list no fixed version.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- Exploited
- Proof of concept public, per CISA
- Fix
- No fix listed
- Who is exposed
- Not reported
Do first: Workaround: The checked facts give no vendor workaround. The affected condition is the exposed .NET Remoting service on TCP port 2001, so limiting network access to that port addresses that condition.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.69% · 53rd percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 50/100
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: yes
- Technical impact: total
Summary
RBH Access Technologies' Integra32 Security Management System is affected. A remote attacker with network access can, without logging in, send crafted serialized data to its deprecated .NET Remoting service on TCP port 2001 and run code as SYSTEM, fully taking over the host.
Original description
RBH Access Technologies Integra32 Security Management System 5.1.11 R5.0 contains an unauthenticated deserialization vulnerability in its deprecated .NET Remoting service, exposed on TCP port 2001 via the AxcvcLt.dll library using BinaryServerFormatterSinkProvider at TypeFilterLevel.Full without requiring authentication. A remote unauthenticated attacker can send a malicious serialized gadget payload (such as a ysoserial.net TypeConfuseDelegate chain) to the IntegraURI object endpoint, or exploit MarshalByRefObject/MarshalByValue unmarshalling for arbitrary file read/write and SMB/NTLMv2 credential coercion, to achieve remote code execution as NT AUTHORITY\SYSTEM and fully compromise the host.
Who should check
Teams running RBH Integra32 Security Management System 5.1.11 R5.0 or earlier with the .NET Remoting service on TCP port 2001 exposed
“Affecting Integra32 Security Management System <= 5.1.11 R5.0”
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.3, total technical impact per CISA
- No patch5/5No patch listed yet
What would change the score
- Would score about 80 if added to CISA KEV
- Would score about 75 if CISA's SSVC rates exploitation active
- Would score about 55 if advisories confirm default setups are exposed
What to do
Workaround: The checked facts give no vendor workaround. The affected condition is the exposed .NET Remoting service on TCP port 2001, so limiting network access to that port addresses that condition.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-63079 (RBH Integra32 5.1.11 .NET Remoting Deserialization RCE), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-63079 (entry last updated 2026-11-16):
Affected:
- RBH Access Technologies Integra32 Security Management System: versions 5.1.11 R5.0
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Integra32 Security Management System version 5.1.11 R5.0 or earlier (source: https://www.vulncheck.com/advisories/rbh-integra32-net-remoting-deserialization-rce)
- The deprecated .NET Remoting service is running and exposed on TCP port 2001 via AxcvcLt.dll (source: https://www.vulncheck.com/advisories/rbh-integra32-net-remoting-deserialization-rce)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-63079 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-63079 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://rbh-access.com/software/integra32/
- https://www.vulncheck.com/advisories/rbh-integra32-net-remoting-deserialization-rce
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-63079
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-63079"}.Public exploit activity
- EPSS: 0.69%
- Posted on X by cve.now Nov 13
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now3 days
- CISA SSVC assessment
Exploitation: poc · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- RBH Access Technologies Integra32 Security Management System
5.1.11 R5.0
Evidence 5
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Public exploit code · 1
Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
- Exploit
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-63079
Is CVE-2026-63079 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A deserialization flaw in the .NET Remoting service lets a remote party run code as the SYSTEM account, fully compromising the host. The same bug is also described as allowing arbitrary file read and write and SMB/NTLMv2 credential coercion.Source: vulncheck.com
Which versions are affected by CVE-2026-63079?
Integra32 Security Management System: version 5.1.11 R5.0.Source: cve.now feed data
Am I affected, and how do I check?
Integra32 Security Management System version 5.1.11 R5.0 or earlier is affected when the deprecated .NET Remoting service is running and exposed on TCP port 2001 through the AxcvcLt.dll library. Check the installed Integra32 version in the product and whether anything is listening on TCP port 2001 on the host.Source: vulncheck.com
How do I fix CVE-2026-63079?
The checked facts name no fixed version and no vendor patch IDs, so no upgrade target can be given from them. Check the vendor's advisory for an update.Source: vulncheck.com
What if there's no patch?
The checked facts give no vendor workaround. The affected condition is the exposed .NET Remoting service on TCP port 2001, so limiting network access to that port addresses that condition.Source: vulncheck.com