Skip to content
  • Hjem
  • Seneste
  • Etiketter
  • Populære
  • Verden
  • Bruger
  • Grupper
Temaer
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Kollaps
FARVEL BIG TECH
  1. Forside
  2. Ikke-kategoriseret
  3. Somebody has leaked CVE-2026-109618 and CVE-2026-109619 in PHP before the patch is out.

Somebody has leaked CVE-2026-109618 and CVE-2026-109619 in PHP before the patch is out.

Planlagt Fastgjort Låst Flyttet Ikke-kategoriseret
243 Indlæg 153 Posters 11 Visninger
  • Ældste til nyeste
  • Nyeste til ældste
  • Most Votes
Svar
  • Svar som emne
Login for at svare
Denne tråd er blevet slettet. Kun brugere med emne behandlings privilegier kan se den.
  • tyalie@chaos.socialT tyalie@chaos.social

    @kallisti @wdormann @GossiTheDog yes it was. But they either took it down afterwards or Twitter has some kind of new "private" setting. Unsure. But I have seen links refer to the video published by Calif's Twitter channel, which didn't work for me through nitter.

    kallisti@infosec.exchangeK This user is from outside of this forum
    kallisti@infosec.exchangeK This user is from outside of this forum
    kallisti@infosec.exchange
    wrote sidst redigeret af
    #72

    @tyalie @wdormann @GossiTheDog

    Ah okay, my bad.

    Thanks for the explanation!

    1 Reply Last reply
    0
    • gossithedog@cyberplace.socialG gossithedog@cyberplace.social

      The PHP situation will lead to a mass of incidents - it’s one of the biggest vulns in years.

      Shodan dork "X-Powered-By: PHP/" - a lot are on EOL versions with no patch. It’s also more hosts as not everybody lists their PHP version in headers.

      joho@mastodon.onlineJ This user is from outside of this forum
      joho@mastodon.onlineJ This user is from outside of this forum
      joho@mastodon.online
      wrote sidst redigeret af
      #73

      @GossiTheDog session.upload_progress.enabled = off

      irina@critter.cafeI 1 Reply Last reply
      0
      • masek@infosec.exchangeM masek@infosec.exchange

        @GossiTheDog You're faster than most commercial services on the issues that matter 😉.

        eingemaischt@chaos.socialE This user is from outside of this forum
        eingemaischt@chaos.socialE This user is from outside of this forum
        eingemaischt@chaos.social
        wrote sidst redigeret af
        #74

        @masek @GossiTheDog I am still wating for debian/ubuntu patches....

        It's a shame that all details are on the table and the embargo is still in place.

        That 3 hours left are a LONG time...

        1 Reply Last reply
        0
        • gossithedog@cyberplace.socialG gossithedog@cyberplace.social

          The screenshot in this tweet is real. https://infosec.exchange/@wdormann/117475540081194496

          gossithedog@cyberplace.socialG This user is from outside of this forum
          gossithedog@cyberplace.socialG This user is from outside of this forum
          gossithedog@cyberplace.social
          wrote sidst redigeret af
          #75

          BSI advisory on PHP:

          https://www.bsi.bund.de/SharedDocs/Cybersicherheitswarnungen/DE/2026/2026-297981-1032.html

          And yes, I agree with everybody it is best to patch where updates are available.

          There *are* mitigations for some of the chain which may be useful as an interim measure - they should be in the PHP advisory I’m guessing, if not I’ll do a blog later.

          SELinux and AppArmor, configured correctly, work well and should be considered regardless.

          simon_m@infosec.exchangeS microplastic@h.pronounmail.comM gossithedog@cyberplace.socialG 3 Replies Last reply
          0
          • gossithedog@cyberplace.socialG gossithedog@cyberplace.social

            A really good mitigation for this btw - AppArmor or SELinux.

            Google something like apparmor restrict php from executing commands. Works against these CVEs.

            Sucks for cybersecurity vendors who shipped their appliances using PHP without SELinux or AppArmor, of course.

            cirio@infosec.exchangeC This user is from outside of this forum
            cirio@infosec.exchangeC This user is from outside of this forum
            cirio@infosec.exchange
            wrote sidst redigeret af
            #76

            @GossiTheDog True, but #SELinux to restrict #php execution is difficult to implement.

            For instance, when using #Apache and #php-fpm, the latter has the same SEL profile as the main apache process and therefore, none of the restrictions of the SEL profile used for PHP scripts. Creating a custom SEL profile for php-fpm is not something you can improvise in half a day.

            1 Reply Last reply
            0
            • gossithedog@cyberplace.socialG gossithedog@cyberplace.social

              BSI advisory on PHP:

              https://www.bsi.bund.de/SharedDocs/Cybersicherheitswarnungen/DE/2026/2026-297981-1032.html

              And yes, I agree with everybody it is best to patch where updates are available.

              There *are* mitigations for some of the chain which may be useful as an interim measure - they should be in the PHP advisory I’m guessing, if not I’ll do a blog later.

              SELinux and AppArmor, configured correctly, work well and should be considered regardless.

              simon_m@infosec.exchangeS This user is from outside of this forum
              simon_m@infosec.exchangeS This user is from outside of this forum
              simon_m@infosec.exchange
              wrote sidst redigeret af
              #77

              @GossiTheDog

              I am still trying to figure out whether I should assume breach by default or whether I am fine checking manually for intrusion.

              The main primary systems and client facing stuff just doesn't use php, so we kinda dodged a bullet.

              1 Reply Last reply
              0
              • gossithedog@cyberplace.socialG gossithedog@cyberplace.social

                BSI advisory on PHP:

                https://www.bsi.bund.de/SharedDocs/Cybersicherheitswarnungen/DE/2026/2026-297981-1032.html

                And yes, I agree with everybody it is best to patch where updates are available.

                There *are* mitigations for some of the chain which may be useful as an interim measure - they should be in the PHP advisory I’m guessing, if not I’ll do a blog later.

                SELinux and AppArmor, configured correctly, work well and should be considered regardless.

                microplastic@h.pronounmail.comM This user is from outside of this forum
                microplastic@h.pronounmail.comM This user is from outside of this forum
                microplastic@h.pronounmail.com
                wrote sidst redigeret af
                #78

                @GossiTheDog still online unlike the dutch ncsc thanks to Java. stay winning, germany lol

                1 Reply Last reply
                0
                • gossithedog@cyberplace.socialG gossithedog@cyberplace.social

                  The PHP situation will lead to a mass of incidents - it’s one of the biggest vulns in years.

                  Shodan dork "X-Powered-By: PHP/" - a lot are on EOL versions with no patch. It’s also more hosts as not everybody lists their PHP version in headers.

                  tomdb@mastodon-belgium.beT This user is from outside of this forum
                  tomdb@mastodon-belgium.beT This user is from outside of this forum
                  tomdb@mastodon-belgium.be
                  wrote sidst redigeret af
                  #79

                  @GossiTheDog so….this vulnerability just grounded the Belgian school system provider. The platform will be down until the vulnerability has been appropriately dealt with. Any idea if the fix is readily available? Just to estimate the amount of downtime.

                  mogwai@social.linux.pizzaM 1 Reply Last reply
                  0
                  • gossithedog@cyberplace.socialG gossithedog@cyberplace.social

                    A really good mitigation for this btw - AppArmor or SELinux.

                    Google something like apparmor restrict php from executing commands. Works against these CVEs.

                    Sucks for cybersecurity vendors who shipped their appliances using PHP without SELinux or AppArmor, of course.

                    bontchev@infosec.exchangeB This user is from outside of this forum
                    bontchev@infosec.exchangeB This user is from outside of this forum
                    bontchev@infosec.exchange
                    wrote sidst redigeret af
                    #80

                    @GossiTheDog Any mitigations for Windows? We have customers running PHP 7 and even 5 who cannot patch (besides, there won't be a patch available for anything but 8).

                    Or should we just prepare for incident response?

                    bontchev@infosec.exchangeB 1 Reply Last reply
                    0
                    • joho@mastodon.onlineJ joho@mastodon.online

                      @GossiTheDog session.upload_progress.enabled = off

                      irina@critter.cafeI This user is from outside of this forum
                      irina@critter.cafeI This user is from outside of this forum
                      irina@critter.cafe
                      wrote sidst redigeret af
                      #81

                      @joho @GossiTheDog as far as we've all been told, that doesn't work.

                      joho@mastodon.onlineJ 1 Reply Last reply
                      0
                      • tomdb@mastodon-belgium.beT tomdb@mastodon-belgium.be

                        @GossiTheDog so….this vulnerability just grounded the Belgian school system provider. The platform will be down until the vulnerability has been appropriately dealt with. Any idea if the fix is readily available? Just to estimate the amount of downtime.

                        mogwai@social.linux.pizzaM This user is from outside of this forum
                        mogwai@social.linux.pizzaM This user is from outside of this forum
                        mogwai@social.linux.pizza
                        wrote sidst redigeret af
                        #82

                        @TomDB @GossiTheDog Php website mentions fixes to be released at 14:00 UTC, i.e. 16:00 CEST.

                        1 Reply Last reply
                        0
                        • irina@critter.cafeI irina@critter.cafe

                          @joho @GossiTheDog as far as we've all been told, that doesn't work.

                          joho@mastodon.onlineJ This user is from outside of this forum
                          joho@mastodon.onlineJ This user is from outside of this forum
                          joho@mastodon.online
                          wrote sidst redigeret af
                          #83

                          @irina

                          Let's wait for the patch then. But it won't hurt.

                          @GossiTheDog

                          1 Reply Last reply
                          0
                          • bontchev@infosec.exchangeB bontchev@infosec.exchange

                            @GossiTheDog Any mitigations for Windows? We have customers running PHP 7 and even 5 who cannot patch (besides, there won't be a patch available for anything but 8).

                            Or should we just prepare for incident response?

                            bontchev@infosec.exchangeB This user is from outside of this forum
                            bontchev@infosec.exchangeB This user is from outside of this forum
                            bontchev@infosec.exchange
                            wrote sidst redigeret af
                            #84

                            @GossiTheDog Additional PoCs and write-ups, supposedly:

                            https://github.com/0x4148/CVE-2026-109618-php2shell-lab

                            https://github.com/syhunt/php2shell-protection

                            https://qideng.substack.com/p/php2shell-dissecting-phps-critical

                            t_var_s@phpc.socialT bontchev@infosec.exchangeB 2 Replies Last reply
                            0
                            • bontchev@infosec.exchangeB bontchev@infosec.exchange

                              @GossiTheDog Additional PoCs and write-ups, supposedly:

                              https://github.com/0x4148/CVE-2026-109618-php2shell-lab

                              https://github.com/syhunt/php2shell-protection

                              https://qideng.substack.com/p/php2shell-dissecting-phps-critical

                              t_var_s@phpc.socialT This user is from outside of this forum
                              t_var_s@phpc.socialT This user is from outside of this forum
                              t_var_s@phpc.social
                              wrote sidst redigeret af
                              #85

                              @bontchev @GossiTheDog Any good ones?

                              bontchev@infosec.exchangeB 1 Reply Last reply
                              0
                              • t_var_s@phpc.socialT t_var_s@phpc.social

                                @bontchev @GossiTheDog Any good ones?

                                bontchev@infosec.exchangeB This user is from outside of this forum
                                bontchev@infosec.exchangeB This user is from outside of this forum
                                bontchev@infosec.exchange
                                wrote sidst redigeret af
                                #86

                                @t_var_s @GossiTheDog Haven't tried any of the PoCs yet; need the admin's permission. The write-ups contain mitigations but warn that they are not completely sufficient. I've also seen claims that making the site read-only (i.e., disable POST requests) prevents the exploit, if you can afford to do it.

                                1 Reply Last reply
                                0
                                • gossithedog@cyberplace.socialG gossithedog@cyberplace.social

                                  BSI advisory on PHP:

                                  https://www.bsi.bund.de/SharedDocs/Cybersicherheitswarnungen/DE/2026/2026-297981-1032.html

                                  And yes, I agree with everybody it is best to patch where updates are available.

                                  There *are* mitigations for some of the chain which may be useful as an interim measure - they should be in the PHP advisory I’m guessing, if not I’ll do a blog later.

                                  SELinux and AppArmor, configured correctly, work well and should be considered regardless.

                                  gossithedog@cyberplace.socialG This user is from outside of this forum
                                  gossithedog@cyberplace.socialG This user is from outside of this forum
                                  gossithedog@cyberplace.social
                                  wrote sidst redigeret af
                                  #87

                                  PHP updates and mitigations are out: https://www.php.net/index.php#2026-10-21-5

                                  keinebasisfuerpalantir@rheinneckar.socialK samuel@social.spejset.orgS centuryavocado@know.me.ukC 3 Replies Last reply
                                  0
                                  • gossithedog@cyberplace.socialG gossithedog@cyberplace.social

                                    The screenshot in this tweet is real. https://infosec.exchange/@wdormann/117475540081194496

                                    aconite33@infosec.exchangeA This user is from outside of this forum
                                    aconite33@infosec.exchangeA This user is from outside of this forum
                                    aconite33@infosec.exchange
                                    wrote sidst redigeret af
                                    #88

                                    @GossiTheDog I sent claude after it just using the source code and the picture posted. Got a PoC working by the time I dropped the kid off at school.

                                    aconite33@infosec.exchangeA 1 Reply Last reply
                                    0
                                    • gossithedog@cyberplace.socialG gossithedog@cyberplace.social

                                      PHP updates and mitigations are out: https://www.php.net/index.php#2026-10-21-5

                                      keinebasisfuerpalantir@rheinneckar.socialK This user is from outside of this forum
                                      keinebasisfuerpalantir@rheinneckar.socialK This user is from outside of this forum
                                      keinebasisfuerpalantir@rheinneckar.social
                                      wrote sidst redigeret af
                                      #89

                                      @GossiTheDog

                                      https://www.php.net/ChangeLog-8.php

                                      1 Reply Last reply
                                      0
                                      • gossithedog@cyberplace.socialG gossithedog@cyberplace.social

                                        PHP updates and mitigations are out: https://www.php.net/index.php#2026-10-21-5

                                        samuel@social.spejset.orgS This user is from outside of this forum
                                        samuel@social.spejset.orgS This user is from outside of this forum
                                        samuel@social.spejset.org
                                        wrote sidst redigeret af
                                        #90

                                        @GossiTheDog but where are the docker images? 🙂

                                        1 Reply Last reply
                                        0
                                        • gossithedog@cyberplace.socialG gossithedog@cyberplace.social

                                          PHP updates and mitigations are out: https://www.php.net/index.php#2026-10-21-5

                                          centuryavocado@know.me.ukC This user is from outside of this forum
                                          centuryavocado@know.me.ukC This user is from outside of this forum
                                          centuryavocado@know.me.uk
                                          wrote sidst redigeret af
                                          #91

                                          @GossiTheDog is php 4 affected (asking for a friend)? 😄

                                          roddie@roddie.socialR 1 Reply Last reply
                                          0
                                          Svar
                                          • Svar som emne
                                          Login for at svare
                                          • Ældste til nyeste
                                          • Nyeste til ældste
                                          • Most Votes


                                          • Log ind

                                          • Login or register to search.
                                          Powered by NodeBB Contributors
                                          Graciously hosted by data.coop
                                          • First post
                                            Last post
                                          0
                                          • Hjem
                                          • Seneste
                                          • Etiketter
                                          • Populære
                                          • Verden
                                          • Bruger
                                          • Grupper