[Bug]: allowInsecure is automatically enabled after subscription update (Hysteria2)

[R0me0Star]

操作系统 / v2rayN / Core 版本

Windows 11 25H2 26200.8875 / v2rayN 7.24.7 / Xray 26.7.28

预期情况

The decoded subscription contains no "insecure" parameter for the Hysteria2 node. The node has a valid Let's Encrypt certificate, so "Allow insecure" should remain disabled after a subscription update.

实际情况

After updating the subscription, "Allow insecure" is enabled on the Hysteria2 node even though the subscription does not contain this parameter. The core then refuses to start the node with:

"Insecure configuration detected: AllowInsecure is enabled but no certificate is provided. This may cause MITM attacks."

This did not happen on 7.24.4 with the same subscription and the same server configuration.

复现方法

1. Set up a Hysteria2 inbound with a valid TLS certificate (Let's Encrypt), no allowInsecure on the server side.
2. Add the subscription URL in v2rayN.
3. Decode the subscription body (base64) and confirm it contains no "insecure" or "allowInsecure" parameter.
4. Update the subscription.
5. Open the Hysteria2 node settings -> Security tab: "Allow insecure" is now enabled.
6. Select the node -> the core reports the insecure configuration warning.

软件日志

2026-08-18.txt

内核日志

----- Message cleared -----
2026.08.18 02:38:53 Subscription update started
2026.08.18 02:38:53 Estonia->Started getting subscriptions
2026.08.18 02:38:53 Estonia->Got subscription content successfully
2026.08.18 02:38:53 Estonia->Start parsing and processing subscription content
2026.08.18 02:38:53 Estonia->Subscription update ended
2026.08.18 02:38:53 -------------------------------------------------------
2026.08.18 02:38:53 Netherlands->Started getting subscriptions
2026.08.18 02:38:53 Netherlands->Got subscription content successfully
2026.08.18 02:38:53 Netherlands->Start parsing and processing subscription content
2026.08.18 02:38:53 Netherlands->Subscription update ended
2026.08.18 02:38:53 -------------------------------------------------------
2026.08.18 02:38:53 Subscription update ended
The current node uses an unencrypted connection, meaning your communications could be directly monitored by network intermediaries controlled by authoritarian governments. For security reasons, nodes of this type cannot connect via Xray-core versions 26.2.6 or higher. If this is a self-built node, please enable TLS or other secure encryption, or pin the certificate using pinSHA256. If this is an airport/provider node, please contact your service provider for a technical upgrade. If the provider refuses to cooperate, it is recommended to switch to a service provider that prioritizes user security. For more information, please visit #9460.
Insecure configuration detected: AllowInsecure is enabled but no certificate is provided. This may cause MITM attacks.
[Hysteria2] Hysteria2(estoniacom:443)
v2rayN - V7.24.7 - X64 | E:\Programs\v2rayN-windows-64\ | E:\Programs\v2rayN-windows-64\v2rayN.exe | Microsoft Windows NT 10.0.26200.0
Starting service (2026.08.18 02:38:53)...
Xray 26.7.28 (Xray, Penetrates Everything.) 5ca6f4b (go1.26.5 windows/amd64)
A unified platform for anti-censorship.
2026/08/18 02:38:54.088540 [Info] infra/conf/serial: Reading config: &{Name:config.json Format:json}
[Hysteria2] Hysteria2(estoniacom:443)
2026/08/18 02:38:54.508050 [Warning] core: Xray 26.7.28 started
2026/08/18 02:38:55.155983 from DNS accepted https://dns.cloudflare.com/dns-query [dns-module -> proxy]
2026/08/18 02:38:55.360808 from tcp:127.0.0.1:7707 accepted tcp:www.google.com:443 [socks -> proxy]
2026.08.18 02:38:55 The delay: 38 ms, none

额外信息

Downgrading to 7.24.4 with the same subscription does not reproduce the issue.
The subscription is generated by 3x-ui.
Related: #9435 (same parameter, different symptom — core fails to start instead of the flag being auto-enabled).

我确认已更新至最新版本

• 是

我确认已查询历史issues

• 是

我确认系统版本是受支持的

• 是