TRENDING
A person sweeping a metal detector across a wet sandy beach with a sea fort on the horizon
November 22, 2026
How to Write YARA Rules With YARA-X to Hunt Malicious Python .pth Startup Files and Measure False Positives Before You Trust Them
A peeling black-and-white metal door standing ajar, with a dark empty hall and bright windows beyond
November 22, 2026
AWS’s “Found a Zero-Day on Their Own” Post Never Names the Product; the Advisory Behind Its Link Shows a Server That Ships With No Login, a README Now Saying Keep It Off the Internet, and a Fix Merged October 19 That PyPI and Docker Hub Still Do Not Carry
A hand paging through index cards in an open wooden library card-catalog drawer labeled Agriculture, with a second drawer open below to the right
November 22, 2026
Microsoft Tells Customers Unauthorized Parties Read Admin Email Addresses and Tenant Metadata Through an Entra Connect Health Flaw Introduced July 23, but Gives No Tenant Count or Start Date, and Its Own Docs Send Tenant Security Notices to the Same Kinds of Contacts
Swimmers in separate lanes of a blue swimming pool, seen from above the water, with lane lines running across the picture
November 22, 2026
How to Size a PostgreSQL Connection Pool in Python: Find Where Throughput Stops Growing, Split max_connections Across Workers, and Stop Slow Handlers From Hoarding Connections
Workers in caps lean over a 1913 Ford assembly line, each assembling parts as they pass on the moving line
November 22, 2026
OpenAI’s Performance Factory Turns Regression Response Into a Task Queue for Agents, but Its Numbers Stop at 600 Root-Caused Cases in 1,700 Investigations and a 70% Grade on 100 Suggestions, and in a Toy World Each of Its Reviewer’s Two Counterfactual Questions Can Return a Confident Wrong Answer
22 Nov 2026
SXZ.io SXZ.io
  • Home
Search the Site
Popular Searches:
Technology Amazon AI
Recent Posts
The sun setting over the sea behind a pyramid-shaped stone monument at Cape Soya, the northernmost point of Japan
How to Retire an API Endpoint in FastAPI: Send Deprecation and Sunset Headers, Find the Clients Still Calling It, Schedule Brownouts, and Block an Early Removal With oasdiff
November 22, 2026
Brass sextant in an open wooden case inside a museum display, an instrument for measuring the angle to the horizon
MIT Technology Review’s “Most Misunderstood Graph” Update Reports METR’s Judgment Findings Mostly Fairly, but It Never Says Each Point Is a 50% Success Rate or Gives the New 3.6-Month Doubling Time and 2.1 to 4.9 Month Range, and It Credits OpenAI With a Comparison METR Built
November 22, 2026
Brass telescope on a wooden tripod inside a white observatory dome with the roof slit open to the sky
Rackspace Says Leaked Credentials Let an Intruder Act as Legitimate Users in Some Spot Customer Organizations and Reach Their Kubernetes Secrets, a Platform9 Co-Founder Names a Breached Observability System as the Root Cause, and the Status Page Says Only “System Maintenance Operations”
November 22, 2026
SXZ.io SXZ.io
  • Home

Categories

Articles 310 Posts
News 316 Posts
Learning Hub 282 Posts
Home/News/Attackers Are Exploiting a Rejetto HFS Flaw Found With Anthropic Mythos, 11 Weeks After the Patch
News

Attackers Are Exploiting a Rejetto HFS Flaw Found With Anthropic Mythos, 11 Weeks After the Patch

VulnCheck says its sensors began seeing exploitation of CVE-2026-61500, a Rejetto HFS admin-session forgery bug that Horizon3 found with Anthropic’s Mythos, on October 1: 80 days after the patch,...

October 3, 2026 6 Min Read
311

VulnCheck says it began detecting exploitation of CVE-2026-61500 on the evening of Thursday, October 1. The flaw is a critical authentication bypass in Rejetto HFS, an open source web file server: an unauthenticated attacker can forge an administrator session cookie and then run code on the server. Horizon3.ai researcher Zach Hanley found it with help from Anthropic’s Mythos model, and VulnCheck researcher Patrick Garrity called it “the second Mythos finding to get reported as exploited in the wild.”

Table Of Content

  • What VulnCheck saw
  • How the chain works
  • Timeline
  • What is new, and what is not
  • What to do

The patch is not new. HFS 3.2.1 shipped on July 13, 80 days before the first sighting, and the NVD record and VulnCheck’s advisory carry the same date. What changed in the past week is that the details went public: a third-party proof-of-concept repository appeared on September 26, and Horizon3 published its write-up on September 30.

What VulnCheck saw

Garrity’s LinkedIn post said “our canaries detected an actor in China targeting real vulnerable hosts in the US.” Canaries are VulnCheck’s own sensors (the company sells a Canary Intelligence product), so these are sightings on its monitoring network. None of the sources we read reports a confirmed compromise of a production HFS server. The Register, which spoke to Garrity, said the first activity came from one IP address in China and targeted vulnerable servers in the US and Japan. On Friday he told the outlet “Today we have seen four hits,” this time from two US addresses in the same subnet, 173.239.211[.]248 and 173.239.211[.]249, which “appear to be coming from a proxy.”

VulnCheck’s advisory says the CVE is in its own KEV catalog. CISA’s Known Exploited Vulnerabilities feed (catalog version 2026.10.02) did not list it when we checked on October 3. HFS has two earlier entries there: CVE-2024-23692, added July 9, 2024, and CVE-2014-6287, added in 2022. The NVD record was published July 13 and still shows a “Deferred” status. It carries VulnCheck’s scores, CVSS 3.1 9.8 and CVSS 4.0 9.3, and the weakness CWE-338, use of a cryptographically weak pseudo-random number generator.

How the chain works

Per NVD, HFS 3.0.0 through 3.2.0 “derives its session-cookie signing key from the non-cryptographic Math.random() generator and discloses outputs of the same generator to unauthenticated clients during login.” We read the vulnerable v3.2.0 source on GitHub, and it matches. When the COOKIE_SIGN_KEYS environment variable is unset, the cookie key is randomId(30), which makes three Math.random() calls at startup (index.ts, cross.ts). The first step of the login handshake sets const sid = Math.random() and keeps it in a session cookie (api.auth.ts). Horizon3’s write-up quotes the model’s analysis describing that cookie as base64-encoded JSON that is signed but not encrypted, so the client can read the value back.

Horizon3’s write-up lists the attack as a short sequence: confirm the admin account exists with a user-enumeration oracle, sample the leaking endpoint 12 times, feed the outputs to the Z3 solver to recover the generator state, step the state backward to the key generated at startup, forge an admin cookie, then use built-in functionality to run code. The public proof of concept, which says it works over HTTP alone, uses six requests and five consecutive values. The built-in functionality is the server_code option, which HFS’s configuration docs describe as “javascript code that works similarly to a plugin.”

The fix is small. Commit 59472e5, dated July 10, swaps the signing key for 32 bytes from Node’s randomBytes() and the handshake value for randomUUID():

// src/index.ts, v3.2.0 (vulnerable)
    || [randomId(30)] // randomness at start gives some extra security, btu also invalidates existing sessions

// src/index.ts, v3.2.1 (fixed)
    || [randomBytes(32).toString('base64url')] // cookie signatures need randomness that cannot be reconstructed from observable Math.random() output

// src/api.auth.ts, v3.2.0 (vulnerable)
            const sid = Math.random()

// src/api.auth.ts, v3.2.1 (fixed)
            const sid = randomUUID()

The same release fixed five more CVEs (CVE-2026-61501 through CVE-2026-61505, per the commit messages) and made the login handler answer unknown usernames the way it answers wrong passwords. The release notes list no CVE numbers. They say only “Multiple security vulnerabilities have been found in all previous versions, potentially allowing an attacker to gain administrative access to HFS.” They also thank Hanley “in collaboration with Claude and Anthropic Research.”

Timeline

2026 What happened
Fri, July 10 Fix commit for CVE-2026-61500 in the HFS repository
Mon, July 13 HFS 3.2.1 released; VulnCheck advisory and NVD record published
Sat, September 26 Third-party proof-of-concept repository created on GitHub
Wed, September 30 Horizon3 publishes its write-up; HFS 3.3.4 released with further security fixes
Thu, October 1 (evening) VulnCheck says its canaries start detecting exploitation
Fri, October 2 Four more hits from two US addresses, per Garrity
Sat, October 3 The Register reports the exploitation

What is new, and what is not

The weakness itself is old. When V8 moved to xorshift128+ in 2015, its team warned that “even though xorshift128+ is a huge improvement over MWC1616, it is still not cryptographically secure.” MDN says Math.random() “does not provide cryptographically secure random numbers” and should not be used for “anything related to security.” Public tools for recovering V8’s generator state also predate this bug by years. TACIXAT’s XorShift128Plus repository, created in 2016, is described as symbolic execution for the algorithm, and StroppaFR’s mathrandomcrack, created in 2024, as “Cracking V8 Math.random() from arbitrary bit leaks.”

What Horizon3 says is new is the model’s role. Its post says Mythos spotted the weak generator, found a separate path that leaks its raw outputs, treated the two as a chain, wrote the Z3 model and produced a working exploit, and “did not require follow-on prompting” to find the leak. “In practice, we do not recall ever seeing an SMT solver being used to attack a cryptographic flaw like this in a real application,” Horizon3 wrote. Horizon3 sells an autonomous pentesting product and its post ends with a demo pitch, so the capability claims are the vendor’s own. The mechanism, though, checks out against the HFS source. We did not run the public exploit code. Horizon3 joined Project Glasswing, Anthropic’s program that gives select partners access to Mythos, in July. Our checklist for AI vulnerability harnesses covers how teams wire such models into a pipeline, and our report on offensive-security researchers and vetted-access programs covers who gets them.

The base rate is a useful check on the headline. Garrity’s tracker lists CVEs that credit Anthropic’s research team, including some from before Project Glasswing was announced. The Register put the count at 286 as of Friday, up from 225 in its September 21 report, and said only one had been exploited until Thursday. That September 21 report named the one exploited then: a critical SQL injection in Ghost, CVE-2026-26980. Two of 286 is 0.7 percent, under the low end of the “just under one percent to two percent” of vulnerabilities that Garrity says historically get weaponized. That arithmetic is ours, and the tracker’s README showed 300 on Saturday, so the share will move. Garrity’s September verdict was that Anthropic’s disclosures aren’t “resulting in different outcomes from a threat perspective than a random selection of other vulnerabilities would.”

Our reading is that the dates point at the public exploit material rather than the model. The release notes have credited Hanley “in collaboration with Claude and Anthropic Research” since July 13, yet VulnCheck’s sensors started seeing exploitation only a day after Horizon3’s write-up and five days after a public exploit repository appeared. No source says which of those, if either, the attacker used, so the timing is a pattern and not proof.

What to do

  • Upgrade. Move to HFS 3.2.1 or later, and prefer the current release. The 3.3.4 release from September 30 lists more fixes: “Security fixes, thanks to @Motan1337 for reporting all of them.”
  • Restrict the admin panel. The admin_net option is documented as a net-mask for the addresses allowed to reach the admin panel, and the default is any address. In the v3.2.0 source, the admin check rejects clients outside that range before it looks at the session’s account.
  • Set a signing key where you cannot upgrade yet. The proof-of-concept’s README says an explicit strong COOKIE_SIGN_KEYS value mitigates signing-key prediction, but that “upgrading remains the recommended remediation.”
  • Look for leftovers. If a 3.0.0 to 3.2.0 server was reachable from the internet, review its server_code setting, its plugin list and its admin logins for anything you did not create, since that is how the chain reaches code execution. That check is our suggestion, drawn from the NVD description.

Tags:

AI SecurityAnthropicAuthentication BypassCryptographyRejetto HFSVulnerability Management

Share

A handwritten word on white paper with a sheet of blue carbon paper peeled back to show a faint carbon copy of the same word underneath
Previous Post

How to Find Near-Duplicate Documents in Python With MinHash and Locality-Sensitive Hashing

Rusted sluice gate winch with a padlock and chain wrapped around its handle
Next Post

The arXiv Two-a-Month Cap Turns Paper Flood Control Into a Bet on the Heavy Tail

No Comment! Be the first one.

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Latest
22 Nov
How to Retire an API Endpoint in FastAPI: Send Deprecation and Sunset Headers, Find the Clients Still Calling It, Schedule Brownouts, and Block an Early Removal With oasdiff
22 Nov
MIT Technology Review’s “Most Misunderstood Graph” Update Reports METR’s Judgment Findings Mostly Fairly, but It Never Says Each Point Is a 50% Success Rate or Gives the New 3.6-Month Doubling Time and 2.1 to 4.9 Month Range, and It Credits OpenAI With a Comparison METR Built
Trending
November 22, 2026
How to Retire an API Endpoint in FastAPI: Send Deprecation and Sunset Headers, Find the Clients Still Calling It, Schedule Brownouts, and Block an Early Removal With oasdiff
November 22, 2026
MIT Technology Review’s “Most Misunderstood Graph” Update Reports METR’s Judgment Findings Mostly Fairly, but It Never Says Each Point Is a 50% Success Rate or Gives the New 3.6-Month Doubling Time and 2.1 to 4.9 Month Range, and It Credits OpenAI With a Comparison METR Built
November 22, 2026
Rackspace Says Leaked Credentials Let an Intruder Act as Legitimate Users in Some Spot Customer Organizations and Reach Their Kubernetes Secrets, a Platform9 Co-Founder Names a Breached Observability System as the Root Cause, and the Status Page Says Only “System Maintenance Operations”
November 21, 2026
How to Write YARA Rules With YARA-X to Hunt Malicious Python .pth Startup Files and Measure False Positives Before You Trust Them
November 21, 2026
AWS’s “Found a Zero-Day on Their Own” Post Never Names the Product; the Advisory Behind Its Link Shows a Server That Ships With No Login, a README Now Saying Keep It Off the Internet, and a Fix Merged October 19 That PyPI and Docker Hub Still Do Not Carry
November 21, 2026
Microsoft Tells Customers Unauthorized Parties Read Admin Email Addresses and Tenant Metadata Through an Entra Connect Health Flaw Introduced July 23, but Gives No Tenant Count or Start Date, and Its Own Docs Send Tenant Security Notices to the Same Kinds of Contacts

Related Posts

Rows of server racks in a data center representing network infrastructure targeted by botnets
News

C0XMO Botnet Shows Why Old Router Firmware Still Matters

June 7, 2026
Close-up of a USB flash drive, representing physical data-theft risk in office security incidents
News

Fake IT Support Is Now Walking Through the Front Door

June 7, 2026
A phone security app on a smartphone resting on a laptop keyboard.
News

Everest Forms Pro Flaw Is Being Exploited to Create Rogue WordPress Admins

June 7, 2026
A customer-support representative wearing a headset against a dark studio background.
Articles

The Meta AI Support Hack Was a Plain Old Authorization Failure

June 7, 2026
SXZ.io SXZ.io
  • [email protected]

Categories

Articles
Learning Hub
News

All Rights Reserved by SXZ.io ©2026