P.K. SHARMA

Cyber security intelligence, AI governance, practitioner analysis

Drupal says an installer flaw can mean site takeover: Critical 18 of 25, discovered by Anthropic's OSS Scanner

Drupal's advisory SA-CORE-2026-017 says that under specific conditions its installer can be used to attempt a reinstall, leading to site takeover or code execution, scored Critical 18 of 25 and credited to Anthropic's OSS Scanner. The conditions are not printed.

By · LinkedIn · · 22 min read

Critical, 18 of 25 (72 percent, derived), with three qualifiers in Drupal's own scoring

On Wednesday 18 November 2026 the Drupal Security Team published SA-CORE-2026-017, "Drupal core - Critical - Remote code execution", for CVE-2026-132165. The advisory says that Drupal core ships with an install.php file and that "Under specific conditions, an attacker can use the installer to attempt to reinstall Drupal." Its risk line scores the flaw 18 of 25, which is 72 percent (derived: 18 divided by 25). The same line carries six letter codes, and Drupal's own hover text on that line, which this site read in the saved page's HTML, defines three of them as qualifiers: the attack needs a "Complex or highly specific" process (AC:Complex), a proof of concept "exists" (E:Proof) and only "uncommon module configurations are exploitable" (TD:Uncommon). Three more point the other way: the line says authentication is "None (all/anonymous users)" (A:None), and that all non-public data is accessible and all data can be modified or deleted (CI:All, II:All).

So the score is both: severe if the conditions are met, and conditional on conditions the advisory does not list. Here is what the page does not establish:

  • The specific conditions. The advisory says there are some and prints none.
  • Whether a site with a locked down installer can be reached at all. The advisory says securing the installer protects against attacks. It does not say it closes every path.
  • Whether anyone is exploiting the flaw. No saved page says so. The advisory prose has no sentence about attacks.
  • How many sites are affected. Not stated.
  • How a scanner found it. The advisory credits Anthropic's OSS Scanner in one sentence and says nothing about the method.
  • A CVSS vector or score. None is printed on any saved page. The score is Drupal's own 25 point scale.

The brief reads Drupal's advisory and installer page as the primary and treats BleepingComputer's report of 19 November as a secondary, used to find the claims to check. This site fetched nothing for this brief: it read pages saved earlier.

Table 1. The figures this brief uses. Counts are made by script over the saved pages; day counts are calendar days (derived).

FigureValueWhere it comes from
Drupal's score18 of 25, 72 percent (derived)The risk line of the advisory; 18 divided by 25.
Branches the advisory tells to update3: 11.4.x to 11.4.13, 11.3.x to 11.3.22, 10.6.x to 10.6.22The Solution field.
End-of-life groups the advisory names4: 11.2.x and below, 10.5.x and below, Drupal 8, Drupal 9The Solution field; no fix line for any.
Entries under Reported By, Fixed By, Coordinated By5, 11 and 13 (counted; no name is printed here)The advisory's credit fields.
Entries in the advisory's contributing organisations list20 (counted)The list the advisory says sponsored time on the release.
Days from the OSS Scanner launch to the advisory41 (derived)Scanner page changelog, 8 October 2026, to 18 November 2026.
Days from the Monday warning BleepingComputer quotes to the advisory2 (derived; the page says only Monday, so 16 November is this site's reading)BleepingComputer, 19 November 2026; the warning itself was not saved.
Installer options and check commands on Drupal's documentation page3 options, 3 curl checksThe saved installer page.

What the risk line defines, and where its numbers stop

The plain text of the advisory prints the line and no key to it. The page's HTML does carry a key: the line is a link to Drupal's page of security risk levels, and the link has a hover text that defines each letter code. This site read that hover text in the saved HTML. Diagram 1 sets each code beside Drupal's wording and beside what the advisory's prose says about the same point.

Drupal's hover text for E reads: "Proof of concept exists (documented methods for developing exploit exist in the wild)" The wording speaks of documented methods, not of an attack on a site. The advisory's prose has no sentence about a proof of concept or about exploitation. Who documented the methods, where, and whether the E:Proof code came from the report or from the Drupal team's own testing are not stated. Whether the saved text supports reading E:Proof as exploitation in the wild is the open point, and this site draws no such conclusion.

The hover text for TD reads "Only uncommon module configurations are exploitable". The advisory's prose describes core's installer and never mentions modules. This site cannot tell whether the TD code refers to contributed modules, to site settings or to something else, and the advisory does not connect the two. What the code does say is that Drupal scored the flaw as reachable only in uncommon setups, and it does not say what they are.

The score itself, 18 of 25, is not explained on any saved page. This site did not save the risk levels page the line links to, so how the six codes add up to 18, and which scores Drupal labels Critical, are not stated in what this site read.

Drawn from the Drupal advisory SA-CORE-2026-017 as saved on 19 November 2026: the risk line from its text and the hover text from its HTML. The bar is drawn to scale from 0 to 25. The 72 percent is derived.

Table 2. The three sentences that carry the story, and what each leaves out. Read from the saved advisory.

The advisory saysStatedNot stated
"This can lead to a site takeover or remote code execution."A reinstall attempt can end in takeover or remote code execution.Whether it always does, or what decides the outcome.
"Under specific conditions, an attacker can use the installer to attempt to reinstall Drupal."Conditions exist. The actor is an attacker, with no sign in mentioned. The act is an attempt.The conditions. What a failed attempt leaves behind. What the installer needs to see.
"Some exploit paths are mitigated if the web server cannot write to or change permissions on settings.php."More than one exploit path exists, and a read only settings.php closes some.Which paths, and which stay open. The word some means the rest are not said to be closed.

The installer, and what Drupal's documentation says to do after installation

The advisory's mechanism is one sentence long. This site reads it as saying that the installer file shipped with core stays reachable on a site that is already installed, and that under conditions it can be driven to reinstall. That is an inference from the advisory's words, not its statement. The advisory does not say what makes a reinstall attempt possible or how an attempt is judged to succeed, and it prints no request, input or code.

Drupal's documentation page, Securing the installer (install.php), says: "Drupal's installer is at /core/install.php." It continues: "You need it once, to install the site." and "After installation is complete, you should block access to it." The page prints Last updated on 18 November 2026, the same date as the advisory, and its Related list links to SA-CORE-2026-017. Whether the page existed before 18 November is not stated on the saved copy.

The page gives its reason: "Drupal has fixed various security issues in the installer over the years" and a site that is already installed does not need the file, so it can "completely remove the risk of future discovered vulnerabilities". Its Related list also names three older items: a public security announcement, PSA-2015-001, titled Remote installation, and two issue queue entries, #3455853 (It should not be possible to install Drupal database into a site where it is already installed) and #1887606 (a possible denial of service by anonymous users triggering database installation tasks at install.php). The saved page does not say how any of the three relates to CVE-2026-132165, and this site draws no link. What the list does show is that Drupal's own documentation treats a reachable installer as a known class of problem.

The page offers three ways to block it, copied in the technical section below: a rule in the web server configuration, which it marks as recommended, a rule in .htaccess for Apache, and removing the file. It adds cautions a reader would otherwise find by breaking something: the Apache rule belongs in the server configuration and not in .htaccess, because the wrong place returns a server error for the whole site; the Nginx rule must not use an exact match, which the page says on some Nginx configurations leaves a URL with extra text after the file name still running the installer; Composer replaces .htaccess every time its scaffold step runs; and "Blocking install.php does not affect updates. update.php is a separate script."

What the documentation does not say. It does not say that blocking the installer closes every path in CVE-2026-132165. The advisory comes closest: under If you cannot upgrade immediately it says to follow the instructions for securing the installer "to protect your site from attacks". It does not say whether the settings.php write protection and the installer block together close everything, and it does not name the paths.

Three branches get a fix, four groups get none, and the printed range has no lower bound

The advisory prints one affected expression, copied in the technical section. Drupal 11.4.x is told to update to 11.4.13, 11.3.x to 11.3.22 and 10.6.x to 10.6.22. For the rest, the advisory says: "Drupal 11.2.x and below are end-of-life and do not receive security coverage." and "Drupal 10.5.x and below are end-of-life and do not receive security coverage." and "Drupal 8 and Drupal 9 have both reached end-of-life." Diagram 2 maps them.

Read as arithmetic, the expression reaches the end-of-life branches. Anything below 10.6.22 is inside its first range, which includes 10.5 and below, Drupal 9 and Drupal 8. Drupal 11.0 to 11.2 sit inside its second range. That is a derived reading of the printed expression, and the advisory itself says only that those branches do not receive security coverage. It prints no fix line for them and says nothing about whether a vendor or a hosting provider might patch them. It does not mention Drupal 7 at all, and its first range has no lower bound, so how far back the flaw reaches is not stated.

The advisory links the three release pages. This site did not save them, so when 11.4.13, 11.3.22 and 10.6.22 shipped, and whether any shipped before 18 November, is not stated on a saved page.

Drawn from the Solution and Affected versions fields of the Drupal advisory as saved on 19 November 2026. The remarks that the printed range reaches the end-of-life branches are this site's reading of the expression.

Discovered by Anthropic's OSS Scanner: what the scanner page says and what it leaves out

The advisory credits the discovery in one sentence: "Discovered by Anthropic's OSS Scanner, as vulnerability ANT-2026-GMRPK0BU." Anthropic's own OSS Scanner page explains the wording. It says: "OSS Scanner is a service by Anthropic to scan open-source repositories for security vulnerabilities." The page asks, but does not require, that a project that patches a finding puts a line like the advisory's, with the report id, in its credits, and says that "Including the ID helps us track the impact this scanner has had". So the credit line in the advisory is the line the scanner page asks for, which is a fact about the wording and not about the finding.

What the page says about the method. Reports go to maintainers who enrol their project. The project supplies a Dockerfile that builds it, and optionally a threat model. Anthropic's side says: "Our pipeline includes agents to double-check bugs, propose patches, and perform root cause analysis." and "We run scanning agents only after fully disabling Internet access inside of hardened sandboxes." The page launched on 8 October 2026 per its changelog, which is 41 days before the advisory (derived). That does not say when the report reached Drupal, which could be before or after the launch, and the saved pages do not give the date.

Two routes, and the page does not say which one applied. The page describes a standard route: Anthropic sends reports after human review, and "By October 2026, we had reviewed over 6,000 such reports." It also describes an optional fast track for projects that want "reports that have not undergone human review", with no disclosure clock: "We will not place any form of 90-day coordinated disclosure period on these unvalidated findings." Neither the advisory nor the scanner page says whether Drupal is enrolled, whether this report took the fast track or the reviewed route, or when Drupal received it. The 6,000 figure counts reports reviewed on the standard route. It is not a count of what the scanner found, of what it found in Drupal, or of what maintainers accepted, and no saved page gives those counts.

What the advisory credits besides the scanner. The Reported By field has 5 entries, one marked as a member of the Drupal Security Team. Fixed By has 11 entries and Coordinated By has 13 (all counted). Twenty entries are listed under contributing organisations, which the advisory says have sponsored time on the release. The advisory names private individuals in those fields and this brief prints none of them. It does not say which entry, if any, relays the scanner's report, so the scanner credit and the reporter list sit side by side without a stated link. That is the answer to the question of what the scanner page's claims leave out: the page speaks about a service, and the advisory's credit is one sentence among several credit fields.

Selling interest, said once. Anthropic builds and sells AI models and published the scanner page. The page says the scanner is at no cost to projects and also describes Claude Security, in its words "our commercial offering", as a separate product. The page is the vendor's own account, and this brief uses it for how the service works and not for any claim about this finding.

The headline says exploits may surface quickly; the advisory says no such thing

BleepingComputer's article of 19 November 2026 is headlined "Drupal patches critical RCE flaw, warns exploits may surface quickly". This site read the whole Drupal advisory. It has no sentence about how fast exploits may appear, or about any attack. The warning in the headline comes from a different page: the article quotes the security team's "Monday advance warning" as saying that exploits "might be developed within hours or days" and that "at least one can be exploited by anonymous users". That warning was not saved, so this site cannot check the wording or the date. Taking Monday as 16 November, it came 2 days before the advisory (derived; the article does not give the date).

The warning speaks of the vulnerabilities in the plural: "The vulnerabilities are currently rated as critical". The article says Drupal also fixed a second flaw on the same day, CVE-2026-132166, which it describes as a moderately critical gadget chain that needs admin privileges. That advisory was also not saved. So the warning's at least one may be this flaw or the other, and the article does not say which. Its own sentence that "anonymous users can exploit it to reinstall the Drupal CMS" is the article's statement, not a quotation of Drupal.

The saved advisory's prose says an attacker, under specific conditions. But its risk line says A:None, which Drupal's hover text defines as "None (all/anonymous users)", so the article's wording agrees with the risk line even where the prose is quieter. Neither says what the conditions are.

Drupal Steward. The advisory says: "Sites that use Drupal Steward are already protected from known attack vectors, but sites should upgrade in the near future in case additional attack vectors are discovered." It does not describe Steward further or say who sells it. The article calls it "the paid Drupal Steward Web Application Firewall (WAF) service". This site did not save a Steward page. Stated once: the article calls Steward a paid service, so the advisory's Steward paragraph points readers to a product the article says is sold. The advisory does not say who sells it, and it does not say whether the known attack vectors include every path of this flaw. The advisory's own advice to Steward customers is to upgrade anyway.

The article adds background this site did not check: an SQL injection flaw Drupal said was exploited in May, a Commerce Core module flaw it says is abused, and a count of Drupal entries in a US government exploited-flaws catalogue. These are the article's statements about other flaws and prove nothing about this one.

Drawn from the four pages as saved on 19 November 2026. Quotations are shortened. Dashed cells are where the page says nothing on the topic.

Where the pages differ, unresolved

The saved pages leave the differences below. This brief reports each and resolves none.

Table 3. Differences between the saved pages.

PointOne page printsAnother page prints
Exploits surfacing quicklyBleepingComputer's headline says Drupal warned exploits may surface quickly.The advisory has no such sentence. Its risk line carries E:Proof. The quoted warning is from a Monday page that was not saved.
Who can exploit itThe advisory prose: an attacker, under specific conditions.BleepingComputer: anonymous users. The advisory's risk line hover text for A:None says all/anonymous users.
Date of the advisoryBleepingComputer: a Wednesday advisory.The advisory: 2026-November-18, which is a Wednesday (derived). The two agree.
The scoreThe advisory: Critical 18 of 25 on Drupal's own scale.No CVSS vector or base score is printed on any saved page, and BleepingComputer prints none.
How the finding is creditedThe advisory: one sentence crediting the OSS Scanner and an ANT id.The advisory also has Reported By, Fixed By and Coordinated By fields. The scanner page speaks of two routes, reviewed and unreviewed, and names no Drupal finding.
StewardThe advisory: protected from known attack vectors; upgrade in the near future.BleepingComputer: a paid Web Application Firewall service. The advisory does not say paid.
The file's pathThe advisory: an install.php file.The documentation and BleepingComputer: /core/install.php. The documentation's checks also request /install.php.

What the pages print: the advisory's fields and Drupal's installer rules

The advisory prints no exploit steps, no request, no input and no indicator, and this brief prints none. What a defender can copy is the advisory's fields and the documentation page's rules. The table lists the fields as printed.

Table 4. The advisory's printed fields, copied from the Drupal advisory as read on 19 November 2026.

FieldAs printedNote
ProjectDrupal core (machine name drupal)As printed.
Date2026-November-18A Wednesday (derived).
Security riskCritical 18 of 25 with six codesSee the risk line block below; the slash in 18 / 25 is a special character.
VulnerabilityRemote code executionAs printed.
CVE IDsCVE-2026-132165No CVE record was read for this brief.
Solution11.4.13, 11.3.22 and 10.6.22Release pages linked from the advisory were not saved.

The first block is the risk line and the affected expression exactly as the advisory prints them. The line holds a special slash character between 18 and 25, copied as printed.

Text
Critical 18 ∕ 25 AC:Complex/A:None/CI:All/II:All/E:Proof/TD:Uncommon

Affected versions
<10.6.22 || >=11.0.0 <11.3.22 || >=11.4.0 <11.4.13
The risk line and the affected versions, copied from the Drupal advisory as read on 19 November 2026.

The next four blocks are the documentation page's own rules. Option 1, which the page marks as recommended, is a rule in the web server configuration. For Apache the page says to add it to the server configuration or virtual host and not to .htaccess, run apachectl configtest before reloading, and add it to every virtual host that serves the site. The page also gives a variant that allows one address only, for adding a site to a multisite setup, which this brief does not copy.

Text
<Location "/core/install.php">
 Require all denied
</Location>
Apache rule for the web server configuration, copied from Drupal's Securing the installer page as read on 19 November 2026. The page says visitors then get a 403 Forbidden response and that the path changes if Drupal is in a subdirectory.

For Nginx the page says to add the rule inside the server block that serves the site over HTTPS, and to run nginx -t before reloading. It explains that the modifier matches every URL that starts with the path, including URLs with extra text after the file name, and that it makes Nginx skip pattern matches such as the one for .php files. It warns: "Do not use an exact match (location = /core/install.php)."

Text
location ^~ /core/install.php {
 return 404;
}
Nginx rule, copied from Drupal's Securing the installer page as read on 19 November 2026.

Option 2 is for Apache sites that cannot edit the server configuration, such as shared hosting. It goes in the .htaccess file in the web root. The page says Apache reads these rules only if AllowOverride includes AuthConfig, which Drupal normally has, and warns that on Composer based sites .htaccess is a scaffold file that Composer replaces whenever the scaffold step runs, so hand edits are lost unless the lines are appended through the scaffold plugin's settings in composer.json. This brief does not copy those settings.

Text
<Files "install.php">
 Require all denied
</Files>
Option 2, .htaccess rule, copied from Drupal's Securing the installer page as read on 19 November 2026.

Option 3 deletes the file. The page says Composer puts the file back every time it installs or updates core, so it must be removed again after each run, and gives these scripts for composer.json. Its listed trade-offs: the removal does not happen if the deployment runs composer install with the no-scripts flag, a new site cannot be installed in the browser until the file is restored, and rm -f does not work on Windows without a Unix style shell. It says Option 1 or 2 is easier to maintain for most sites.

Text
"scripts": {
 "post-install-cmd": ["rm -f web/core/install.php"],
 "post-update-cmd": ["rm -f web/core/install.php"]
}
Option 3, Composer scripts that delete the file, copied from Drupal's Securing the installer page as read on 19 November 2026. The page says to change web/ if the web root has another name.

Last, the page's three checks, with example.com to be replaced by the site's address. It says: "All three should end with a 403 or 404 response. If you see 200, the block is not working." It then says to check that the site still works normally and that database updates still run, with drush updatedb or /update.php. The three paths are worth noting: the first is the file under core, the second is install.php at the root with redirects followed, and the third has extra text after the file name.

Text
curl -I https://example.com/core/install.php
curl -IL https://example.com/install.php
curl -I https://example.com/core/install.php/foo
The three check commands, copied from Drupal's Securing the installer page as read on 19 November 2026.

What to do, in order

Items 1, 2 and 5 are Drupal's own advice. The rest is this site's suggestion and is marked.

Take this with you

Drupal says: upgrade to 11.4.13, 11.3.22 or 10.6.22, and secure the installer after installation. The suggestions follow.

  • Drupal's advice: update Drupal 11.4.x to 11.4.13, 11.3.x to 11.3.22 and 10.6.x to 10.6.22. Find every Drupal site you run first, including multisite installs, staging copies and sites run for others.
  • Drupal's advice: secure the installer after installation, as its documentation says. The page marks a rule in the web server configuration as recommended. Run the three printed curl checks and expect 403 or 404, then check that updates still run, because the page says update.php is a separate script.
  • This site's suggestion: ask any managed host whether the installer is already blocked. The page says some platforms already block it and to test before adding a rule.
  • This site's suggestion: if you run 11.2.x or earlier, 10.5.x or earlier, Drupal 8 or Drupal 9, plan a move. The advisory prints no fix for them, and the only interim step it prints for sites that cannot upgrade is to secure the installer.
  • Drupal's statement, not a fix: some exploit paths are mitigated if the web server cannot write to or change permissions on settings.php. Check that permission, and do not treat it as the answer, because the word is some.
  • Drupal's advice: Steward customers should still upgrade, because the advisory says to upgrade in the near future in case additional attack vectors are discovered.
  • This site's suggestion: search web server logs for requests to the installer paths printed above, including paths with extra text after the file name, going back as far as the logs allow and at least to the Monday warning BleepingComputer quotes. A request is not proof of an attack, and the saved pages print no indicator of compromise.
  • This site's suggestion: keep the evidence of what was running and when, such as lock files, deployment records and the date of each update, so a later answer about exposure can be checked.

The question the advisory leaves open

Drupal scored the flaw Critical and, in the same line, told readers it needs a complex process and an uncommon configuration, but it printed neither. A site owner who cannot see the conditions cannot tell whether the site falls outside them, so the only answer the advisory gives is to upgrade and block the installer. Which of the unlisted conditions would have to hold for your site to be reachable, and who at Drupal or at the scanner's maker could say?

Key facts

Sources

  1. PrimarySA-CORE-2026-017, Drupal core, Critical, Remote code execution, dated 2026-November-18: risk line and its hover text, affected versions, CVE-2026-132165, description, credit line, Drupal Steward paragraph, solution. Read in full; saved 19 November 2026 at about 17:23 UTCDrupal.org (Drupal Security Team)accessed 2026-11-19
  2. PrimarySecuring the installer (install.php), Last updated on 18 November 2026: why to block it, three options, the check commands, related items. Read in full; saved 19 November 2026 at about 17:23 UTCDrupal.org documentationaccessed 2026-11-19
  3. PrimaryOSS Scanner, the vendor's own page: how the service works, the two reporting routes, attribution wording, changelog from 8 October 2026. Read in full; saved 19 November 2026 at about 17:23 UTCAnthropic (red.anthropic.com)accessed 2026-11-19
  4. Reported byDrupal patches critical RCE flaw, warns exploits may surface quickly, 19 November 2026: a secondary, used to find the claims to check against the advisory. Saved 19 November 2026 at about 16:32 UTCBleepingComputeraccessed 2026-11-19

Share this briefing

Know someone who owns this problem? Send it to them.

Related briefings

The briefing, in your inbox

Practitioner analysis of cyber and AI security news. No vendor noise.

How often

Every new briefing in one email, at 7am, or at 7am, 12:30pm and 6pm. Nothing is sent when nothing is new. Unsubscribe any time.