Scans for Proxmox Servers, (Wed, Sep 9th)
A vulnerability in older versions of Proxmox VE version 7, which is no longer supported, was disclosed about a week ago. Following the advisory, there has been an increase in scanning activity targeting Proxmox servers, particularly on port 8006, along with brute force login attempts against the API endpoints. The scans and brute force attempts are observable in server logs with HTTP status codes 401 and 308. The vulnerability affects only version 7 of Proxmox VE, which has been unsupported for several years.
AI Analysis
Technical Summary
Proxmox published an advisory revealing a vulnerability affecting only Proxmox VE version 7, which has not been supported for a couple of years. Since the disclosure, there has been a noticeable increase in scanning and brute force attempts targeting Proxmox servers, especially on port 8006. Attackers are attempting to authenticate via the /api2/json/access/ticket and /api2/extjs/access/ticket endpoints, with failed login attempts logged as HTTP 401 or 308 status codes. The 308 status code indicates a redirect allowing method change, which can occur if the attacker initially sends a non-TLS POST request. The vulnerability and associated scanning activity appear limited to the unsupported version 7 of Proxmox VE.
Potential Impact
The vulnerability affects only Proxmox VE version 7, which is no longer supported. The increased scanning and brute force attempts could lead to unauthorized access if the vulnerability is successfully exploited on vulnerable systems. However, no active exploits in the wild have been confirmed. Systems running unsupported versions remain at risk if exposed to the internet without additional protections.
Mitigation Recommendations
Since Proxmox VE version 7 is no longer supported, users should upgrade to a supported version of Proxmox VE to eliminate exposure to this vulnerability. Systems still running version 7 should be isolated from untrusted networks or have additional access controls to prevent unauthorized access. Monitoring for brute force attempts and blocking suspicious IPs may reduce risk. Patch status is not confirmed in the provided data; users should consult the official Proxmox advisory for current remediation guidance.
Scans for Proxmox Servers, (Wed, Sep 9th)
Description
A vulnerability in older versions of Proxmox VE version 7, which is no longer supported, was disclosed about a week ago. Following the advisory, there has been an increase in scanning activity targeting Proxmox servers, particularly on port 8006, along with brute force login attempts against the API endpoints. The scans and brute force attempts are observable in server logs with HTTP status codes 401 and 308. The vulnerability affects only version 7 of Proxmox VE, which has been unsupported for several years.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Proxmox published an advisory revealing a vulnerability affecting only Proxmox VE version 7, which has not been supported for a couple of years. Since the disclosure, there has been a noticeable increase in scanning and brute force attempts targeting Proxmox servers, especially on port 8006. Attackers are attempting to authenticate via the /api2/json/access/ticket and /api2/extjs/access/ticket endpoints, with failed login attempts logged as HTTP 401 or 308 status codes. The 308 status code indicates a redirect allowing method change, which can occur if the attacker initially sends a non-TLS POST request. The vulnerability and associated scanning activity appear limited to the unsupported version 7 of Proxmox VE.
Potential Impact
The vulnerability affects only Proxmox VE version 7, which is no longer supported. The increased scanning and brute force attempts could lead to unauthorized access if the vulnerability is successfully exploited on vulnerable systems. However, no active exploits in the wild have been confirmed. Systems running unsupported versions remain at risk if exposed to the internet without additional protections.
Defensive Guidance
Since Proxmox VE version 7 is no longer supported, users should upgrade to a supported version of Proxmox VE to eliminate exposure to this vulnerability. Systems still running version 7 should be isolated from untrusted networks or have additional access controls to prevent unauthorized access. Monitoring for brute force attempts and blocking suspicious IPs may reduce risk. Patch status is not confirmed in the provided data; users should consult the official Proxmox advisory for current remediation guidance.
Technical Details
- Classification
- {"confidence":0.3,"severitySource":"default","classifier":"rss-v2"}
- Article Source
- {"url":"https://isc.sans.edu/diary/rss/33324","fetched":true,"fetchedAt":"2026-09-09T17:52:15.025Z","wordCount":458}
Threat ID: 6aa19ccfacd9273b49aa5c68
Added to database: 09/09/2026, 17:52:15 UTC
Last enriched: 09/09/2026, 17:52:21 UTC
Last updated: 09/09/2026, 20:13:20 UTC
Views: 9
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.