On this page (7 sections)

The NVD page for CVE-2026-63079 describes an unauthenticated deserialization vulnerability in RBH Access Technologies Integra32 Security Management System 5.1.11 R5.0. According to the description, a remote attacker with network access to the affected service can run code as NT AUTHORITY\SYSTEM, which means full control of the Windows host.

If your organization or a client runs this product, it is worth a same-day check of who can reach that server on the network. The information available is thin, so this article separates what is stated from what is still unknown.

What has been published so far

The only source available is the NVD description. The structured CVE data we have is empty (no CVSS score, no severity, no CWE, no references, no package list), and our research notes say the CVE has no NVD record yet, even though the NVD page text supplies a description and a 2026-11-13 date. These points are inconsistent, so treat the record as incomplete and subject to change rather than as a finished entry.

No vendor advisory and no other independent confirmation was found.

Not yet confirmed: a patched version, a vendor advisory, a CVSS score, and any evidence of exploitation in the wild. Check the vendor and NVD directly for updates rather than relying on this summary.

Technical details in plain terms

Per the NVD description, the product exposes a deprecated .NET Remoting service on TCP port 2001 through the AxcvcLt.dll library. The service uses BinaryServerFormatterSinkProvider at TypeFilterLevel.Full and does not require authentication.

Deserialization flaws arise when a program rebuilds objects from data sent by a client. With binary formatters and the most permissive type filter level, the sender can influence which object types are created. If the server will instantiate attacker-chosen types, code that already exists in the application can be chained into unintended actions. Here, the description says no login step stands in the way.

The description lists several outcomes an unauthenticated remote attacker could reach through that service:

  • Remote code execution as NT AUTHORITY\SYSTEM, the highest-privileged local account on Windows.
  • Arbitrary file read and write through MarshalByRefObject or MarshalByValue unmarshalling.
  • SMB/NTLMv2 credential coercion, where the server is made to authenticate to a host the attacker controls, which can expose password hashes.

The description also names a public serialization-gadget tool as an example of how such a payload could be built. This article does not include payload details, and the research does not say whether working exploits for this specific product are circulating.

Who is exposed

The description covers Integra32 Security Management System 5.1.11 R5.0. The research does not say whether other versions are affected or unaffected, so treat adjacent versions as unknown until the vendor says otherwise.

Realistic exposure depends on network reachability of TCP port 2001 on the Integra32 server. As a general assessment, not a finding from the research:

  • Highest risk: the port is reachable from the internet or from broad corporate, guest or vendor networks.
  • Moderate risk: the port is reachable only from a flat internal network where any compromised workstation could connect.
  • Lower risk: the server sits in a tightly segmented network where only named administrator or controller hosts can reach the port.

The description calls the service deprecated and says it is exposed on TCP 2001. It does not say whether the service listens by default or only when configured, so confirm on your own server rather than assuming either way.

How to check your exposure

Start by confirming whether you run the affected version and whether anything can reach the port. These checks are read-only.

On the Integra32 server (Windows), list listeners on TCP port 2001 and the owning process ID. A line showing LISTENING on port 2001 means something is accepting connections there:

List listeners on TCP 2001 (run in an elevated Command Prompt on the Windows server)Windows command
netstat -ano | findstr :2001

From a different machine on a network segment that should not have access, test whether the port is reachable. If TcpTestSucceeded shows True, that segment can connect and your firewall rules need tightening:

Test reachability of TCP 2001 from another host (PowerShell; replace the address with your server's)PowerShell
Test-NetConnection -ComputerName 192.0.2.10 -Port 2001

For internet exposure, check your edge firewall and port-forwarding rules for anything mapping to the server on port 2001, and review what external scanning shows for your public addresses. A Webforta Scan can help review your public-facing websites, but a service like this may only be visible from inside your network, so verify the firewall rules directly.

What to do now

No fixed version is named in the available source, so the priority is reducing who can talk to the service while you contact the vendor.

  1. Inventory every Integra32 installation and record the exact version; identify any running 5.1.11 R5.0.
  2. Block inbound TCP port 2001 to the server at the network firewall and at the Windows host firewall, allowing only specific, trusted management hosts if the service is genuinely needed.
  3. Confirm the port is not forwarded or published to the internet, and remove any such rule.
  4. Contact RBH Access Technologies for a security advisory, a fixed release or an official mitigation, and ask whether the deprecated Remoting service can be disabled.
  5. Restrict who can log on to and reach the server; put it in its own network segment away from general user workstations.
  6. Block or monitor outbound SMB (TCP 445) from the server to untrusted destinations, since the description mentions NTLMv2 credential coercion.
  7. Review the host for signs of compromise: unexpected processes started by the Integra32 service, new local accounts or services, and unusual outbound connections.
  8. If you suspect misuse, treat credentials used on that server as exposed and rotate them after containment.
Caution. Changing firewall rules on a server that may be relied on for building operations can lock out legitimate controllers or workstations. Confirm which hosts need port 2001 before blocking it, and apply changes in a maintenance window with a rollback plan.

On the server, you can review current connections to port 445 to see whether it is talking SMB to unexpected hosts. Look for remote addresses you do not recognize:

List connections involving port 445 and look for unexpected SMB peers (elevated Command Prompt on…Windows command
netstat -ano | findstr :445

Detection and monitoring afterwards

Because the described attack path is a network service, network telemetry is your best signal. Alert on new or unusual connections to TCP port 2001 from hosts outside the approved list, and on the server initiating SMB or other outbound sessions to addresses it has never contacted before. On the host, watch for child processes spawned by the Integra32 service and for new services, scheduled tasks or local administrators.

Keep watching the NVD entry and the vendor's channels. Because the record is incomplete, a CVSS score, references and fix information may appear later and could change the urgency.

A web application firewall does not protect a raw TCP service such as this one; network-level controls are what apply here. For general background, see our guides on what a WAF does and small business website security.

Bottom line

The published description points to an unauthenticated, network-reachable path to SYSTEM-level code execution on the host running Integra32 5.1.11 R5.0, which is serious if the port is reachable. What is missing is just as important: no confirmed fix, no CVSS score, no vendor advisory and no word on exploitation. Until the vendor responds, limiting network access to TCP port 2001 is the most effective step available.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-63079: RBH Access Technologies Integra32 Security Management System 5.1.11 R5.0 contains an unauthenticated deserialization vulnerability in its deprecated .NET…nvd.nist.gov ·
  • CVE-2026-63079
  • RBH Access Technologies
  • deserialization
  • remote code execution
  • Integra32