⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● High · CVSS 7.7

How to Fix CVE-2026-21665: Unsafe deserialization in Originate Loans Peripherals (formerly Velocity Services) -- Print Service component

By Sai Kiran Pandrala. Last verified: 2026-05-25.

CVE-2026-21665 is a unsafe deserialization in Fiserv Originate Loans Peripherals (formerly Velocity Services) -- Print Service component. The fix is to apply the vendor patch noted below.

⚡ At a glance
Severity7.7 (High)
Actively exploited?No public listing in CISA KEV
AffectedOriginate Loans Peripherals (formerly Velocity Services) -- Print Service component 2021.2.4 to <2021.2.4
Fixed inSee vendor advisory
Type (CWE)CWE-502 Deserialization of Untrusted Data

What is CVE-2026-21665?

The Print Service component of Fiserv Originate Loans Peripherals (formerly Velocity Services) in unsupported version 2021.2.4 (build 4.7.3155.0011) uses deprecated .NET Remoting TCP channels that allow unsafe deserialization of untrusted data. When these services are exposed to an untrusted network in a client-managed deployment, an unauthenticated attacker can achieve remote code execution. Version 2021.2.4 is no longer supported by Fiserv. Customers should upgrade to a currently supported release (2025.1 or later) and ensure that .NET Remoting service ports are not exposed beyond trusted network boundaries.

This CVE documents behavior observed in a client-hosted deployment running an unsupported legacy version of Originate Loans Peripherals with .NET Remoting ports exposed to an untrusted network. This is not a default or supported configuration. Customers running legacy versions should upgrade to a currently supported release and ensure .NET Remoting ports are restricted to trusted network segments. The finding does not apply to Fiserv-hosted environments. The CVSS base score is 7.7 (High), which puts this in the upper risk band and warrants a fast patch cycle. The official advisory is at https://learn.microsoft.com/en-us/dotnet/core/compatibility/core-libraries/5.0/remoting-apis-obsolete.

Am I affected?

Check the version of Originate Loans Peripherals (formerly Velocity Services) -- Print Service component you are running and compare it against the Affected row above (Originate Loans Peripherals (formerly Velocity Services) -- Print Service component 2021.2.4 to <2021.2.4). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:


# Linux package check
dpkg -s originate-loans-peripherals-formerly-velocity-services----print-service-component 2>/dev/null | grep -i ^Version
rpm -q originate-loans-peripherals-formerly-velocity-services----print-service-component 2>/dev/null
command -v originate-loans-peripherals-formerly-velocity-services----print-service-component >/dev/null && originate-loans-peripherals-formerly-velocity-services----print-service-component --version 2>/dev/null


# Windows (PowerShell)
Get-Package -Name "*Originate Loans Peripherals (formerly Velocity Services) -- Print Service component*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "Originate Loans Peripherals (formerly Velocity Services) -- Print Service component" 2>$null

How to fix CVE-2026-21665

Upgrade Originate Loans Peripherals (formerly Velocity Services) -- Print Service component to a patched build: See vendor advisory. The vendor advisory is the source of truth for the exact fixed version.

Ubuntu / Debian


sudo apt-get update
sudo apt-get install --only-upgrade originate-loans-peripherals-formerly-velocity-services----print-service-component
dpkg -s originate-loans-peripherals-formerly-velocity-services----print-service-component | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux


sudo dnf upgrade --refresh originate-loans-peripherals-formerly-velocity-services----print-service-component -y
# or for older releases:
sudo yum update originate-loans-peripherals-formerly-velocity-services----print-service-component -y
rpm -q originate-loans-peripherals-formerly-velocity-services----print-service-component

SUSE / openSUSE


sudo zypper refresh
sudo zypper update originate-loans-peripherals-formerly-velocity-services----print-service-component
rpm -q originate-loans-peripherals-formerly-velocity-services----print-service-component

Complete PowerShell remediation script (Windows)


# Fix script for CVE-2026-21665 affecting Originate Loans Peripherals (formerly Velocity Services) -- Print Service component
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-21665-fix-$(Get-Date -Format yyyyMMdd-HHmmss).log"
New-Item -ItemType Directory -Force (Split-Path $LogPath) | Out-Null
Start-Transcript -Path $LogPath -Append

try {
    Write-Host "[1/4] Detect installed version"
    $pkg = Get-Package -Name "*Originate Loans Peripherals (formerly Velocity Services) -- Print Service component*" -ErrorAction SilentlyContinue
    if ($pkg) { $pkg | Format-Table Name, Version }
    else { Write-Host "Not detected via Get-Package; try winget list" }

    Write-Host "[2/4] Backup configuration"
    $backup = "C:\Backup\originate-loans-peripherals-formerly-velocity-services----print-service-component-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\Originate Loans Peripherals (formerly Velocity Services) -- Print Service component" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Apply the upgrade to See vendor advisory"
    winget upgrade --name "Originate Loans Peripherals (formerly Velocity Services) -- Print Service component" --silent --accept-source-agreements --accept-package-agreements
    if ($LASTEXITCODE -ne 0) {
        # Fallback: pull latest via OS update channel
        Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
        Import-Module PSWindowsUpdate
        Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
    }

    Write-Host "[4/4] Verify the patched build"
    winget list --name "Originate Loans Peripherals (formerly Velocity Services) -- Print Service component"
    Write-Host "Patch applied. Reboot if prompted."
    exit 0
} catch {
    Write-Error "Patch failed: $_"
    exit 1
} finally {
    Stop-Transcript
}

Complete Bash remediation script (Linux)


#!/usr/bin/env bash
# Fix script for CVE-2026-21665 affecting Originate Loans Peripherals (formerly Velocity Services) -- Print Service component
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-21665-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1

echo "[1/4] Detect installed version"
if command -v dpkg >/dev/null; then
    dpkg -s originate-loans-peripherals-formerly-velocity-services----print-service-component 2>/dev/null | grep -i ^Version || echo "originate-loans-peripherals-formerly-velocity-services----print-service-component not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q originate-loans-peripherals-formerly-velocity-services----print-service-component || echo "originate-loans-peripherals-formerly-velocity-services----print-service-component not installed via rpm"
fi

echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-21665-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/originate-loans-peripherals-formerly-velocity-services----print-service-component /etc/originate-loans-peripherals-formerly-velocity-services----print-service-component.d /etc/originate-loans-peripherals-formerly-velocity-services----print-service-component.conf; do
    [ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done

echo "[3/4] Apply the upgrade (target: See vendor advisory)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y originate-loans-peripherals-formerly-velocity-services----print-service-component
elif command -v dnf >/dev/null; then
    dnf upgrade --refresh -y originate-loans-peripherals-formerly-velocity-services----print-service-component
elif command -v yum >/dev/null; then
    yum update -y originate-loans-peripherals-formerly-velocity-services----print-service-component
elif command -v zypper >/dev/null; then
    zypper --non-interactive update originate-loans-peripherals-formerly-velocity-services----print-service-component
fi

echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
    dpkg -s originate-loans-peripherals-formerly-velocity-services----print-service-component 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
    rpm -q originate-loans-peripherals-formerly-velocity-services----print-service-component
fi
echo "Done. Restart any service that loaded the old library."

If you can't patch immediately

Apply at least one of the following inline controls until you can deploy the patched build. None replace the upgrade.

Restrict exposure with nftables (Linux)


# Allow only trusted CIDR to reach the affected service ports
sudo nft add table inet filter 2>/dev/null || true
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }' 2>/dev/null || true
sudo nft 'add rule inet filter input tcp dport {80, 443} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset

Block at the host firewall (Windows)


New-NetFirewallRule -DisplayName "Block-CVE-2026-21665" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-21665"

Disable the affected service (Linux)


sudo systemctl stop originate-loans-peripherals-formerly-velocity-services----print-service-component 2>/dev/null || true
sudo systemctl disable originate-loans-peripherals-formerly-velocity-services----print-service-component 2>/dev/null || true

If the vendor advisory lists an official workaround, prefer that wording verbatim. If no workaround is published, the only safe remediation is the patch.

How to verify the fix worked

After upgrading, confirm the installed version matches the patched build and that no old library is still loaded by a long-running process.


# Linux
dpkg -s originate-loans-peripherals-formerly-velocity-services----print-service-component 2>/dev/null | grep -i ^Version
rpm -q originate-loans-peripherals-formerly-velocity-services----print-service-component 2>/dev/null || true
# Pid map check for old library handles
sudo lsof +c0 2>/dev/null | grep -i "DEL.*lib" || true


# Windows
Get-Package -Name "*Originate Loans Peripherals (formerly Velocity Services) -- Print Service component*" | Select-Object Name, Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above See vendor advisory. Restart the affected service (systemctl restart <service> on Linux, or restart the Windows service) so it loads the patched binary.

Frequently asked questions

Other vulnerabilities in the same area that are worth patching alongside this one:

Is CVE-2026-21665 actively exploited?

There is no public confirmation of exploitation in the wild listed in CISA KEV at the time of this writing. Patch anyway. Public exploits commonly follow disclosure within weeks.

Do I need to reboot after patching CVE-2026-21665?

For kernel and OS-level updates, yes. For most userland packages a systemctl restart <service> is enough on Linux, and restarting the Windows service or app on Windows. Any process that loaded the old library keeps using it until restarted.

What is the CVSS score for CVE-2026-21665?

7.7 (High). Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N.

Where is the official advisory for CVE-2026-21665?

The vendor advisory is at https://learn.microsoft.com/en-us/dotnet/core/compatibility/core-libraries/5.0/remoting-apis-obsolete. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-21665.

References

*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*